Communication and Data Processing in Wireless Communications

ABSTRACT

Wireless communications may be used to support data processing. A plurality of resources may be indicated for a wireless device to use to communicate and/or process data. Data may be received and processed based on groups of the plurality of resources to be used. For example, the plurality of resources to be used may be associated with different resource groups.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/877,038, filed on Jul. 22, 2019. The above-referenced application ishereby incorporated by reference in its entirety.

BACKGROUND

A base station and a wireless device in a communication networkestablish and use channels for signal transmissions. The wireless devicereceives downlink channel transmissions, from the base station, todetermine uplink transmissions.

SUMMARY

The following summary presents a simplified summary of certain features.The summary is not an extensive overview and is not intended to identifykey or critical elements.

Wireless communications may be used to support data processing. Aplurality of resources may be indicated for a wireless device to use tocommunicate and/or process data. At least some data may be indicated tobe processed in-order, out-of-order, and/or overlapping with other data.Data may be processed based on groups of the plurality of resources tobe used. For example, the plurality of resources to be used may beassociated with different resource groups. A wireless device may becapable of processing out-of-order and/or overlapping data transmissionsif the wireless device is configured to use different resource groups,whereas a wireless device may not be capable of processing out-of-orderand/or overlapping data transmissions if the wireless device is notconfigured to use different resource groups. Additionally oralternatively, data processing may be performed based on a priorityindication (or lack thereof) in a message for processing data. Forexample, if a message does not comprise, or lacks, a priorityindication, a wireless device may not process data associated with themessage. Various operations described herein may provide advantages suchas improved channel processing efficiencies, improved system throughput,reduced misalignment between a base station and a wireless device,reduced overhead/retransmissions, and/or reduced delay/latency ofcommunication.

These and other features and advantages are described in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

Some features are shown by way of example, and not by limitation, in theaccompanying drawings. In the drawings, like numerals reference similarelements.

FIG. 1A and FIG. 1B show example communication networks.

FIG. 2A shows an example user plane.

FIG. 2B shows an example control plane configuration.

FIG. 3 shows example of protocol layers.

FIG. 4A shows an example downlink data flow for a user planeconfiguration.

FIG. 4B shows an example format of a Medium Access Control (MAC)subheader in a MAC Protocol Data Unit (PDU).

FIG. 5A shows an example mapping for downlink channels.

FIG. 5B shows an example mapping for uplink channels.

FIG. 6 shows example radio resource control (RRC) states and RRC statetransitions.

FIG. 7 shows an example configuration of a frame.

FIG. 8 shows an example resource configuration of one or more carriers.

FIG. 9 shows an example configuration of bandwidth parts (BWPs).

FIG. 10A shows example carrier aggregation configurations based oncomponent carriers.

FIG. 10B shows example group of cells.

FIG. 11A shows an example mapping of one or more synchronizationsignal/physical broadcast channel (SS/PBCH) blocks.

FIG. 11B shows an example mapping of one or more channel stateinformation reference signals (CSI-RSs).

FIG. 12A shows examples of downlink beam management procedures.

FIG. 12B shows examples of uplink beam management procedures.

FIG. 13A shows an example four-step random access procedure.

FIG. 13B shows an example two-step random access procedure.

FIG. 13C shows an example two-step random access procedure.

FIG. 14A shows an example of control resource set (CORESET)configurations.

FIG. 14B shows an example of a control channel element to resourceelement group (CCE-to-REG) mapping.

FIG. 15A shows an example of communications between a wireless deviceand a base station.

FIG. 15B shows example elements of a computing device that may be usedto implement any of the various devices described herein

FIG. 16A, FIG. 16B, FIG. 16C, and FIG. 16D show examples of uplink anddownlink signal transmission.

FIG. 17A, FIG. 17B, and FIG. 17C show example MAC subheaders.

FIG. 18A and FIG. 18B show example MAC PDUs.

FIG. 19 shows example LCID values.

FIG. 20 shows example LCID values.

FIG. 21A and FIG. 21B show example SCell Activation/Deactivation MACCEs.

FIG. 22 shows an example of bandwidth part (BWP) management.

FIG. 23 shows an example of a HARQ entity configured with multiple HARQprocesses.

FIG. 24 shows an example uplink (re)transmission.

FIG. 25 shows an example downlink (re)transmission.

FIG. 26A and FIG. 26B show examples of out-of-order processing.

FIG. 27 shows an example of a prioritization for HARQ processing.

FIG. 28 shows an example of out-of-order processing.

FIG. 29 shows an example out-of-order processing.

FIG. 30A and FIG. 30B show examples of out-of-order processing.

FIG. 31 shows an example of out-of-order grant processing.

FIG. 32A shows example communications for multiple transmissionreception points (TRPs) and multiple antenna panels.

FIG. 32B shows an example of transmission and reception via multipleTRPs and/or multiple antenna panels.

FIG. 33, FIG. 34A, and FIG. 34B show example out-of-order processing formultiple TRPs and/or multiple antenna panels.

FIG. 35A and FIG. 35B show example out-of-order processing for multipleTRPs and/or multiple antenna panels.

FIG. 36 shows an example of out-of-order processing for multiple TRPsand/or multiple antenna panels.

FIG. 37 shows an example of out-of-order processing for multiple TRPsand/or multiple antenna panels.

DETAILED DESCRIPTION

The accompanying drawings and descriptions provide examples. It is to beunderstood that the examples shown in the drawings and/or described arenon-exclusive, and that features shown and described may be practiced inother examples. Examples are provided for operation of wirelesscommunication systems, which may be used in the technical field ofmulticarrier communication systems. More particularly, the technologydisclosed herein may relate to processing of downlink channels anduplink channels.

FIG. 1A shows an example communication network 100. The communicationnetwork 100 may comprise a mobile communication network). Thecommunication network 100 may comprise, for example, a public landmobile network (PLMN) operated/managed/run by a network operator. Thecommunication network 100 may comprise one or more of a core network(CN) 102, a radio access network (RAN) 104, and/or a wireless device106. The communication network 100 may comprise, and/or a device withinthe communication network 100 may communicate with (e.g., via CN 102),one or more data networks (DN(s)) 108. The wireless device 106 maycommunicate with one or more DNs 108, such as public DNs (e.g., theInternet), private DNs, and/or intra-operator DNs. The wireless device106 may communicate with the one or more DNs 108 via the RAN 104 and/orvia the CN 102. The CN 102 may provide/configure the wireless device 106with one or more interfaces to the one or more DNs 108. As part of theinterface functionality, the CN 102 may set up end-to-end connectionsbetween the wireless device 106 and the one or more DNs 108,authenticate the wireless device 106, provide/configure chargingfunctionality, etc.

The wireless device 106 may communicate with the RAN 104 via radiocommunications over an air interface. The RAN 104 may communicate withthe CN 102 via various communications (e.g., wired communications and/orwireless communications). The wireless device 106 may establish aconnection with the CN 102 via the RAN 104. The RAN 104 mayprovide/configure scheduling, radio resource management, and/orretransmission protocols, for example, as part of the radiocommunications. The communication direction from the RAN 104 to thewireless device 106 over/via the air interface may be referred to as thedownlink and/or downlink communication direction. The communicationdirection from the wireless device 106 to the RAN 104 over/via the airinterface may be referred to as the uplink and/or uplink communicationdirection. Downlink transmissions may be separated and/or distinguishedfrom uplink transmissions, for example, based on at least one of:frequency division duplexing (FDD), time-division duplexing (TDD), anyother duplexing schemes, and/or one or more combinations thereof.

As used throughout, the term “wireless device” may comprise one or moreof: a mobile device, a fixed (e.g., non-mobile) device for whichwireless communication is configured or usable, a computing device, anode, a device capable of wirelessly communicating, or any other devicecapable of sending and/or receiving signals. As non-limiting examples, awireless device may comprise, for example: a telephone, a cellularphone, a Wi-Fi phone, a smartphone, a tablet, a computer, a laptop, asensor, a meter, a wearable device, an Internet of Things (IoT) device,a hotspot, a cellular repeater, a vehicle road side unit (RSU), a relaynode, an automobile, a wireless user device (e.g., user equipment (UE),a user terminal (UT), etc.), an access terminal (AT), a mobile station,a handset, a wireless transmit and receive unit (WTRU), a wirelesscommunication device, and/or any combination thereof.

The RAN 104 may comprise one or more base stations (not shown). As usedthroughout, the term “base station” may comprise one or more of: a basestation, a node, a Node B (NB), an evolved NodeB (eNB), a gNB, anng-eNB, a relay node (e.g., an integrated access and backhaul (IAB)node), a donor node (e.g., a donor eNB, a donor gNB, etc.), an accesspoint (e.g., a Wi-Fi access point), a transmission and reception point(TRP), a computing device, a device capable of wirelessly communicating,or any other device capable of sending and/or receiving signals. A basestation may comprise one or more of each element listed above. Forexample, a base station may comprise one or more TRPs. As othernon-limiting examples, a base station may comprise for example, one ormore of: a Node B (e.g., associated with Universal MobileTelecommunications System (UMTS) and/or third-generation (3G)standards), an Evolved Node B (eNB) (e.g., associated withEvolved-Universal Terrestrial Radio Access (E-UTRA) and/orfourth-generation (4G) standards), a remote radio head (RRH), a basebandprocessing unit coupled to one or more remote radio heads (RRHs), arepeater node or relay node used to extend the coverage area of a donornode, a Next Generation Evolved Node B (ng-eNB), a Generation Node B(gNB) (e.g., associated with NR and/or fifth-generation (SG) standards),an access point (AP) (e.g., associated with, for example, Wi-Fi or anyother suitable wireless communication standard), any other generationbase station, and/or any combination thereof. A base station maycomprise one or more devices, such as at least one base station centraldevice (e.g., a gNB Central Unit (gNB-CU)) and at least one base stationdistributed device (e.g., a gNB Distributed Unit (gNB-DU)).

A base station (e.g., in the RAN 104) may comprise one or more sets ofantennas for communicating with the wireless device 106 wirelessly(e.g., via an over the air interface). One or more base stations maycomprise sets (e.g., three sets or any other quantity of sets) ofantennas to respectively control multiple cells or sectors (e.g., threecells, three sectors, any other quantity of cells, or any other quantityof sectors). The size of a cell may be determined by a range at which areceiver (e.g., a base station receiver) may successfully receivetransmissions from a transmitter (e.g., a wireless device transmitter)operating in the cell. One or more cells of base stations (e.g., byalone or in combination with other cells) may provide/configure a radiocoverage to the wireless device 106 over a wide geographic area tosupport wireless device mobility. A base station comprising threesectors (e.g., or n-sector, where n refers to any quantity n) may bereferred to as a three-sector site (e.g., or an n-sector site) or athree-sector base station (e.g., an n-sector base station).

One or more base stations (e.g., in the RAN 104) may be implemented as asectored site with more or less than three sectors. One or more basestations of the RAN 104 may be implemented as an access point, as abaseband processing device/unit coupled to several RRHs, and/or as arepeater or relay node used to extend the coverage area of a node (e.g.,a donor node). A baseband processing device/unit coupled to RRHs may bepart of a centralized or cloud RAN architecture, for example, where thebaseband processing device/unit may be centralized in a pool of basebandprocessing devices/units or virtualized. A repeater node may amplify andsend (e.g., transmit, retransmit, rebroadcast, etc.) a radio signalreceived from a donor node. A relay node may perform the substantiallythe same/similar functions as a repeater node. The relay node may decodethe radio signal received from the donor node, for example, to removenoise before amplifying and sending the radio signal.

The RAN 104 may be deployed as a homogenous network of base stations(e.g., macrocell base stations) that have similar antenna patternsand/or similar high-level transmit powers. The RAN 104 may be deployedas a heterogeneous network of base stations (e.g., different basestations that have different antenna patterns). In heterogeneousnetworks, small cell base stations may be used to provide/configuresmall coverage areas, for example, coverage areas that overlap withcomparatively larger coverage areas provided/configured by other basestations (e.g., macrocell base stations). The small coverage areas maybe provided/configured in areas with high data traffic (or so-called“hotspots”) or in areas with a weak macrocell coverage. Examples ofsmall cell base stations may comprise, in order of decreasing coveragearea, microcell base stations, picocell base stations, and femtocellbase stations or home base stations.

Examples described herein may be used in a variety of types ofcommunications. For example, communications may be in accordance withthe Third-Generation Partnership Project (3GPP) (e.g., one or morenetwork elements similar to those of the communication network 100),communications in accordance with Institute of Electrical andElectronics Engineers (IEEE), communications in accordance withInternational Telecommunication Union (ITU), communications inaccordance with International Organization for Standardization (ISO),etc. The 3GPP has produced specifications for multiple generations ofmobile networks: a 3G network known as UMTS, a 4G network known asLong-Term Evolution (LTE) and LTE Advanced (LTE-A), and a 5G networkknown as 5G System (5GS) and NR system. 3GPP may produce specificationsfor additional generations of communication networks (e.g., 6G and/orany other generation of communication network). Examples may bedescribed with reference to one or more elements (e.g., the RAN) of a3GPP 5G network, referred to as a next-generation RAN (NG-RAN), or anyother communication network, such as a 3GPP network and/or a non-3GPPnetwork. Examples described herein may be applicable to othercommunication networks, such as 3G and/or 4G networks, and communicationnetworks that may not yet be finalized/specified (e.g., a 3GPP 6Gnetwork), satellite communication networks, and/or any othercommunication network. NG-RAN implements and updates 5G radio accesstechnology referred to as NR and may be provisioned to implement 4Gradio access technology and/or other radio access technologies, such asother 3GPP and/or non-3GPP radio access technologies.

FIG. 1B shows an example communication network 150. The communicationnetwork may comprise a mobile communication network. The communicationnetwork 150 may comprise, for example, a PLMN operated/managed/run by anetwork operator. The communication network 150 may comprise one or moreof: a CN 152 (e.g., a 5G core network (5G-CN)), a RAN 154 (e.g., anNG-RAN), and/or wireless devices 156A and 156B (collectively wirelessdevice(s) 156). The communication network 150 may comprise, and/or adevice within the communication network 150 may communicate with (e.g.,via CN 152), one or more data networks (DN(s)) 170. These components maybe implemented and operate in substantially the same or similar manneras corresponding components described with respect to FIG. 1A.

The CN 152 (e.g., 5G-CN) may provide/configure the wireless device(s)156 with one or more interfaces to one or more DNs 170, such as publicDNs (e.g., the Internet), private DNs, and/or intra-operator DNs. Aspart of the interface functionality, the CN 152 (e.g., 5G-CN) may set upend-to-end connections between the wireless device(s) 156 and the one ormore DNs, authenticate the wireless device(s) 156, and/orprovide/configure charging functionality. The CN 152 (e.g., the 5G-CN)may be a service-based architecture, which may differ from other CNs(e.g., such as a 3GPP 4G CN). The architecture of nodes of the CN 152(e.g., 5G-CN) may be defined as network functions that offer servicesvia interfaces to other network functions. The network functions of theCN 152 (e.g., 5G CN) may be implemented in several ways, for example, asnetwork elements on dedicated or shared hardware, as software instancesrunning on dedicated or shared hardware, and/or as virtualized functionsinstantiated on a platform (e.g., a cloud-based platform).

The CN 152 (e.g., 5G-CN) may comprise an Access and Mobility ManagementFunction (AMF) device 158A and/or a User Plane Function (UPF) device158B, which may be separate components or one component AMF/UPF device158. The UPF device 158B may serve as a gateway between a RAN 154 (e.g.,NG-RAN) and the one or more DNs 170. The UPF device 158B may performfunctions, such as: packet routing and forwarding, packet inspection anduser plane policy rule enforcement, traffic usage reporting, uplinkclassification to support routing of traffic flows to the one or moreDNs 170, quality of service (QoS) handling for the user plane (e.g.,packet filtering, gating, uplink/downlink rate enforcement, and uplinktraffic verification), downlink packet buffering, and/or downlink datanotification triggering. The UPF device 158B may serve as an anchorpoint for intra-/inter-Radio Access Technology (RAT) mobility, anexternal protocol (or packet) data unit (PDU) session point ofinterconnect to the one or more DNs, and/or a branching point to supporta multi-homed PDU session. The wireless device(s) 156 may be configuredto receive services via a PDU session, which may be a logical connectionbetween a wireless device and a DN.

The AMF device 158A may perform functions, such as: Non-Access Stratum(NAS) signaling termination, NAS signaling security, Access Stratum (AS)security control, inter-CN node signaling for mobility between accessnetworks (e.g., 3GPP access networks and/or non-3GPP networks), idlemode wireless device reachability (e.g., idle mode UE reachability forcontrol and execution of paging retransmission), registration areamanagement, intra-system and inter-system mobility support, accessauthentication, access authorization including checking of roamingrights, mobility management control (e.g., subscription and policies),network slicing support, and/or session management function (SMF)selection. NAS may refer to the functionality operating between a CN anda wireless device, and AS may refer to the functionality operatingbetween a wireless device and a RAN.

The CN 152 (e.g., 5G-CN) may comprise one or more additional networkfunctions that may not be shown in FIG. 1B. The CN 152 (e.g., 5G-CN) maycomprise one or more devices implementing at least one of: a SessionManagement Function (SMF), an NR Repository Function (NRF), a PolicyControl Function (PCF), a Network Exposure Function (NEF), a UnifiedData Management (UDM), an Application Function (AF), an AuthenticationServer Function (AUSF), and/or any other function.

The RAN 154 (e.g., NG-RAN) may communicate with the wireless device(s)156 via radio communications (e.g., an over the air interface). Thewireless device(s) 156 may communicate with the CN 152 via the RAN 154.The RAN 154 (e.g., NG-RAN) may comprise one or more first-type basestations (e.g., gNBs comprising a gNB 160A and a gNB 160B (collectivelygNBs 160)) and/or one or more second-type base stations (e.g., ng eNBscomprising an ng-eNB 162A and an ng-eNB 162B (collectively ng eNBs162)). The RAN 154 may comprise one or more of any quantity of types ofbase station. The gNBs 160 and ng eNBs 162 may be referred to as basestations. The base stations (e.g., the gNBs 160 and ng eNBs 162) maycomprise one or more sets of antennas for communicating with thewireless device(s) 156 wirelessly (e.g., an over an air interface). Oneor more base stations (e.g., the gNBs 160 and/or the ng eNBs 162) maycomprise multiple sets of antennas to respectively control multiplecells (or sectors). The cells of the base stations (e.g., the gNBs 160and the ng-eNBs 162) may provide a radio coverage to the wirelessdevice(s) 156 over a wide geographic area to support wireless devicemobility.

The base stations (e.g., the gNBs 160 and/or the ng-eNBs 162) may beconnected to the CN 152 (e.g., 5G CN) via a first interface (e.g., an NGinterface) and to other base stations via a second interface (e.g., anXn interface). The NG and Xn interfaces may be established using directphysical connections and/or indirect connections over an underlyingtransport network, such as an internet protocol (IP) transport network.The base stations (e.g., the gNBs 160 and/or the ng-eNBs 162) maycommunicate with the wireless device(s) 156 via a third interface (e.g.,a Uu interface). A base station (e.g., the gNB 160A) may communicatewith the wireless device 156A via a Uu interface. The NG, Xn, and Uuinterfaces may be associated with a protocol stack. The protocol stacksassociated with the interfaces may be used by the network elements shownin FIG. 1B to exchange data and signaling messages. The protocol stacksmay comprise two planes: a user plane and a control plane. Any otherquantity of planes may be used (e.g., in a protocol stack). The userplane may handle data of interest to a user. The control plane mayhandle signaling messages of interest to the network elements.

One or more base stations (e.g., the gNBs 160 and/or the ng-eNBs 162)may communicate with one or more AMF/UPF devices, such as the AMF/UPF158, via one or more interfaces (e.g., NG interfaces). A base station(e.g., the gNB 160A) may be in communication with, and/or connected to,the UPF 158B of the AMF/UPF 158 via an NG-User plane (NG-U) interface.The NG-U interface may provide/perform delivery (e.g., non-guaranteeddelivery) of user plane PDUs between a base station (e.g., the gNB 160A)and a UPF device (e.g., the UPF 158B). The base station (e.g., the gNB160A) may be in communication with, and/or connected to, an AMF device(e.g., the AMF 158A) via an NG-Control plane (NG-C) interface. The NG-Cinterface may provide/perform, for example, NG interface management,wireless device context management (e.g., UE context management),wireless device mobility management (e.g., UE mobility management),transport of NAS messages, paging, PDU session management, configurationtransfer, and/or warning message transmission.

A wireless device may access the base station, via an interface (e.g.,Uu interface), for the user plane configuration and the control planeconfiguration. The base stations (e.g., gNBs 160) may provide user planeand control plane protocol terminations towards the wireless device(s)156 via the Uu interface. A base station (e.g., the gNB 160A) mayprovide user plane and control plane protocol terminations toward thewireless device 156A over a Uu interface associated with a firstprotocol stack. A base station (e.g., the ng-eNBs 162) may provideEvolved UMTS Terrestrial Radio Access (E UTRA) user plane and controlplane protocol terminations towards the wireless device(s) 156 via a Uuinterface (e.g., where E UTRA may refer to the 3GPP 4G radio-accesstechnology). A base station (e.g., the ng-eNB 162B) may provide E UTRAuser plane and control plane protocol terminations towards the wirelessdevice 156B via a Uu interface associated with a second protocol stack.The user plane and control plane protocol terminations may comprise, forexample, NR user plane and control plane protocol terminations, 4G userplane and control plane protocol terminations, etc.

The CN 152 (e.g., 5G-CN) may be configured to handle one or more radioaccesses (e.g., NR, 4G, and/or any other radio accesses). It may also bepossible for an NR network/device (or any first network/device) toconnect to a 4G core network/device (or any second network/device) in anon-standalone mode (e.g., non-standalone operation). In anon-standalone mode/operation, a 4G core network may be used to provide(or at least support) control-plane functionality (e.g., initial access,mobility, and/or paging). Although only one AMF/UPF 158 is shown in FIG.1B, one or more base stations (e.g., one or more gNBs and/or one or moreng-eNBs) may be connected to multiple AMF/UPF nodes, for example, toprovide redundancy and/or to load share across the multiple AMF/UPFnodes.

An interface (e.g., Uu, Xn, and/or NG interfaces) between networkelements (e.g., the network elements shown in FIG. 1B) may be associatedwith a protocol stack that the network elements may use to exchange dataand signaling messages. A protocol stack may comprise two planes: a userplane and a control plane. Any other quantity of planes may be used(e.g., in a protocol stack). The user plane may handle data associatedwith a user (e.g., data of interest to a user). The control plane mayhandle data associated with one or more network elements (e.g.,signaling messages of interest to the network elements).

The communication network 100 in FIG. 1A and/or the communicationnetwork 150 in FIG. 1B may comprise any quantity/number and/or type ofdevices, such as, for example, computing devices, wireless devices,mobile devices, handsets, tablets, laptops, internet of things (IoT)devices, hotspots, cellular repeaters, computing devices, and/or, moregenerally, user equipment (e.g., UE). Although one or more of the abovetypes of devices may be referenced herein (e.g., UE, wireless device,computing device, etc.), it should be understood that any device hereinmay comprise any one or more of the above types of devices or similardevices. The communication network, and any other network referencedherein, may comprise an LTE network, a 5G network, a satellite network,and/or any other network for wireless communications (e.g., any 3GPPnetwork and/or any non-3GPP network). Apparatuses, systems, and/ormethods described herein may generally be described as implemented onone or more devices (e.g., wireless device, base station, eNB, gNB,computing device, etc.), in one or more networks, but it will beunderstood that one or more features and steps may be implemented on anydevice and/or in any network.

FIG. 2A shows an example user plane configuration. The user planeconfiguration may comprise, for example, an NR user plane protocolstack. FIG. 2B shows an example control plane configuration. The controlplane configuration may comprise, for example, an NR control planeprotocol stack. One or more of the user plane configuration and/or thecontrol plane configuration may use a Uu interface that may be between awireless device 210 and a base station 220. The protocol stacks shown inFIG. 2A and FIG. 2B may be substantially the same or similar to thoseused for the Uu interface between, for example, the wireless device 156Aand the base station 160A shown in FIG. 1B.

A user plane configuration (e.g., an NR user plane protocol stack) maycomprise multiple layers (e.g., five layers or any other quantity oflayers) implemented in the wireless device 210 and the base station 220(e.g., as shown in FIG. 2A). At the bottom of the protocol stack,physical layers (PHYs) 211 and 221 may provide transport services to thehigher layers of the protocol stack and may correspond to layer 1 of theOpen Systems Interconnection (OSI) model. The protocol layers above PHY211 may comprise a medium access control layer (MAC) 212, a radio linkcontrol layer (RLC) 213, a packet data convergence protocol layer (PDCP)214, and/or a service data application protocol layer (SDAP) 215. Theprotocol layers above PHY 221 may comprise a medium access control layer(MAC) 222, a radio link control layer (RLC) 223, a packet dataconvergence protocol layer (PDCP) 224, and/or a service data applicationprotocol layer (SDAP) 225. One or more of the four protocol layers abovePHY 211 may correspond to layer 2, or the data link layer, of the OSImodel. One or more of the four protocol layers above PHY 221 maycorrespond to layer 2, or the data link layer, of the OSI model.

FIG. 3 shows an example of protocol layers. The protocol layers maycomprise, for example, protocol layers of the NR user plane protocolstack. One or more services may be provided between protocol layers.SDAPs (e.g., SDAPS 215 and 225 shown in FIG. 2A and FIG. 3) may performQuality of Service (QoS) flow handling. A wireless device (e.g., thewireless devices 106, 156A, 156B, and 210) may receive servicesthrough/via a PDU session, which may be a logical connection between thewireless device and a DN. The PDU session may have one or more QoS flows310. A UPF (e.g., the UPF 158B) of a CN may map IP packets to the one ormore QoS flows of the PDU session, for example, based on one or more QoSrequirements (e.g., in terms of delay, data rate, error rate, and/or anyother quality/service requirement). The SDAPs 215 and 225 may performmapping/de-mapping between the one or more QoS flows 310 and one or moreradio bearers 320 (e.g., data radio bearers). The mapping/de-mappingbetween the one or more QoS flows 310 and the radio bearers 320 may bedetermined by the SDAP 225 of the base station 220. The SDAP 215 of thewireless device 210 may be informed of the mapping between the QoS flows310 and the radio bearers 320 via reflective mapping and/or controlsignaling received from the base station 220. For reflective mapping,the SDAP 225 of the base station 220 may mark the downlink packets witha QoS flow indicator (QFI), which may bemonitored/detected/identified/indicated/observed by the SDAP 215 of thewireless device 210 to determine the mapping/de-mapping between the oneor more QoS flows 310 and the radio bearers 320.

PDCPs (e.g., the PDCPs 214 and 224 shown in FIG. 2A and FIG. 3) mayperform header compression/decompression, for example, to reduce theamount of data that may need to be transmitted over the air interface,ciphering/deciphering to prevent unauthorized decoding of datatransmitted over the air interface, and/or integrity protection (e.g.,to ensure control messages originate from intended sources). The PDCPs214 and 224 may perform retransmissions of undelivered packets,in-sequence delivery and reordering of packets, and/or removal ofpackets received in duplicate due to, for example, a handover (e.g., anintra-gNB handover). The PDCPs 214 and 224 may perform packetduplication, for example, to improve the likelihood of the packet beingreceived. A receiver may receive the packet in duplicate and may removeany duplicate packets. Packet duplication may be useful for certainservices, such as services that require high reliability.

The PDCP layers (e.g., PDCPs 214 and 224) may perform mapping/de-mappingbetween a split radio bearer and RLC channels (e.g., RLC channels 330)(e.g., in a dual connectivity scenario/configuration). Dual connectivitymay refer to a technique that allows a wireless device to communicatewith multiple cells (e.g., two cells) or, more generally, multiple cellgroups comprising: a master cell group (MCG) and a secondary cell group(SCG). A split bearer may be configured and/or used, for example, if asingle radio bearer (e.g., such as one of the radio bearersprovided/configured by the PDCPs 214 and 224 as a service to the SDAPs215 and 225) is handled by cell groups in dual connectivity. The PDCPs214 and 224 may map/de-map between the split radio bearer and RLCchannels 330 belonging to the cell groups.

RLC layers (e.g., RLCs 213 and 223) may perform segmentation,retransmission via Automatic Repeat Request (ARQ), and/or removal ofduplicate data units received from MAC layers (e.g., MACs 212 and 222,respectively). The RLC layers (e.g., RLCs 213 and 223) may supportmultiple transmission modes (e.g., three transmission modes: transparentmode (TM); unacknowledged mode (UM); and acknowledged mode (AM)). TheRLC layers may perform one or more of the noted functions, for example,based on the transmission mode an RLC layer is operating. The RLCconfiguration may be per logical channel. The RLC configuration may notdepend on numerologies and/or Transmission Time Interval (TTI) durations(or other durations). The RLC layers (e.g., RLCs 213 and 223) mayprovide/configure RLC channels as a service to the PDCP layers (e.g.,PDCPs 214 and 224, respectively), such as shown in FIG. 3.

The MAC layers (e.g., MACs 212 and 222) may performmultiplexing/demultiplexing of logical channels and/or mapping betweenlogical channels and transport channels. The multiplexing/demultiplexingmay comprise multiplexing/demultiplexing of data units/data portions,belonging to the one or more logical channels, into/from TransportBlocks (TBs) delivered to/from the PHY layers (e.g., PHYs 211 and 221,respectively). The MAC layer of a base station (e.g., MAC 222) may beconfigured to perform scheduling, scheduling information reporting,and/or priority handling between wireless devices via dynamicscheduling. Scheduling may be performed by a base station (e.g., thebase station 220 at the MAC 222) for downlink/or and uplink. The MAClayers (e.g., MACs 212 and 222) may be configured to perform errorcorrection(s) via Hybrid Automatic Repeat Request (HARQ) (e.g., one HARQentity per carrier in case of Carrier Aggregation (CA)), priorityhandling between logical channels of the wireless device 210 via logicalchannel prioritization and/or padding. The MAC layers (e.g., MACs 212and 222) may support one or more numerologies and/or transmissiontimings. Mapping restrictions in a logical channel prioritization maycontrol which numerology and/or transmission timing a logical channelmay use. The MAC layers (e.g., the MACs 212 and 222) mayprovide/configure logical channels 340 as a service to the RLC layers(e.g., the RLCs 213 and 223).

The PHY layers (e.g., PHYs 211 and 221) may perform mapping of transportchannels to physical channels and/or digital and analog signalprocessing functions, for example, for sending and/or receivinginformation (e.g., via an over the air interface). The digital and/oranalog signal processing functions may comprise, for example,coding/decoding and/or modulation/demodulation. The PHY layers (e.g.,PHYs 211 and 221) may perform multi-antenna mapping. The PHY layers(e.g., the PHYs 211 and 221) may provide/configure one or more transportchannels (e.g., transport channels 350) as a service to the MAC layers(e.g., the MACs 212 and 222, respectively).

FIG. 4A shows an example downlink data flow for a user planeconfiguration. The user plane configuration may comprise, for example,the NR user plane protocol stack shown in FIG. 2A. One or more TBs maybe generated, for example, based on a data flow via a user planeprotocol stack. As shown in FIG. 4A, a downlink data flow of three IPpackets (n, n+1, and m) via the NR user plane protocol stack maygenerate two TBs (e.g., at the base station 220). An uplink data flowvia the NR user plane protocol stack may be similar to the downlink dataflow shown in FIG. 4A. The three IP packets (n, n+1, and m) may bedetermined from the two TBs, for example, based on the uplink data flowvia an NR user plane protocol stack. A first quantity of packets (e.g.,three or any other quantity) may be determined from a second quantity ofTBs (e.g., two or another quantity).

The downlink data flow may begin, for example, if the SDAP 225 receivesthe three IP packets (or other quantity of IP packets) from one or moreQoS flows and maps the three packets (or other quantity of packets) toradio bearers (e.g., radio bearers 402 and 404). The SDAP 225 may mapthe IP packets n and n+1 to a first radio bearer 402 and map the IPpacket m to a second radio bearer 404. An SDAP header (labeled with “H”preceding each SDAP SDU shown in FIG. 4A) may be added to an IP packetto generate an SDAP PDU, which may be referred to as a PDCP SDU. Thedata unit transferred from/to a higher protocol layer may be referred toas a service data unit (SDU) of the lower protocol layer, and the dataunit transferred to/from a lower protocol layer may be referred to as aprotocol data unit (PDU) of the higher protocol layer. As shown in FIG.4A, the data unit from the SDAP 225 may be an SDU of lower protocollayer PDCP 224 (e.g., PDCP SDU) and may be a PDU of the SDAP 225 (e.g.,SDAP PDU).

Each protocol layer (e.g., protocol layers shown in FIG. 4A) or at leastsome protocol layers may: perform its own function(s) (e.g., one or morefunctions of each protocol layer described with respect to FIG. 3), adda corresponding header, and/or forward a respective output to the nextlower layer (e.g., its respective lower layer). The PDCP 224 may performan IP-header compression and/or ciphering. The PDCP 224 may forward itsoutput (e.g., a PDCP PDU, which is an RLC SDU) to the RLC 223. The RLC223 may optionally perform segmentation (e.g., as shown for IP packet min FIG. 4A). The RLC 223 may forward its outputs (e.g., two RLC PDUs,which are two MAC SDUs, generated by adding respective subheaders to twoSDU segments (SDU Segs)) to the MAC 222. The MAC 222 may multiplex anumber of RLC PDUs (MAC SDUs). The MAC 222 may attach a MAC subheader toan RLC PDU (MAC SDU) to form a TB. The MAC subheaders may be distributedacross the MAC PDU (e.g., in an NR configuration as shown in FIG. 4A).The MAC subheaders may be entirely located at the beginning of a MAC PDU(e.g., in an LTE configuration). The NR MAC PDU structure may reduce aprocessing time and/or associated latency, for example, if the MAC PDUsubheaders are computed before assembling the full MAC PDU.

FIG. 4B shows an example format of a MAC subheader in a MAC PDU. A MACPDU may comprise a MAC subheader (H) and a MAC SDU. Each of one or moreMAC subheaders may comprise an SDU length field for indicating thelength (e.g., in bytes) of the MAC SDU to which the MAC subheadercorresponds; a logical channel identifier (LCID) field foridentifying/indicating the logical channel from which the MAC SDUoriginated to aid in the demultiplexing process; a flag (F) forindicating the size of the SDU length field; and a reserved bit (R)field for future use.

One or more MAC control elements (CEs) may be added to, or insertedinto, the MAC PDU by a MAC layer, such as MAC 223 or MAC 222. As shownin FIG. 4B, two MAC CEs may be inserted/added before two MAC PDUs. TheMAC CEs may be inserted/added at the beginning of a MAC PDU for downlinktransmissions (as shown in FIG. 4B). One or more MAC CEs may beinserted/added at the end of a MAC PDU for uplink transmissions. MAC CEsmay be used for in band control signaling. Example MAC CEs may comprisescheduling-related MAC CEs, such as buffer status reports and powerheadroom reports; activation/deactivation MAC CEs (e.g., MAC CEs foractivation/deactivation of PDCP duplication detection, channel stateinformation (CSI) reporting, sounding reference signal (SRS)transmission, and prior configured components); discontinuous reception(DRX)-related MAC CEs; timing advance MAC CEs; and random access-relatedMAC CEs. A MAC CE may be preceded by a MAC subheader with a similarformat as described for the MAC subheader for MAC SDUs and may beidentified with a reserved value in the LCID field that indicates thetype of control information included in the corresponding MAC CE.

FIG. 5A shows an example mapping for downlink channels. The mapping foruplink channels may comprise mapping between channels (e.g., logicalchannels, transport channels, and physical channels) for downlink. FIG.5B shows an example mapping for uplink channels. The mapping for uplinkchannels may comprise mapping between channels (e.g., logical channels,transport channels, and physical channels) for uplink. Information maybe passed through/via channels between the RLC, the MAC, and the PHYlayers of a protocol stack (e.g., the NR protocol stack). A logicalchannel may be used between the RLC and the MAC layers. The logicalchannel may be classified/indicated as a control channel that may carrycontrol and/or configuration information (e.g., in the NR controlplane), or as a traffic channel that may carry data (e.g., in the NRuser plane). A logical channel may be classified/indicated as adedicated logical channel that may be dedicated to a specific wirelessdevice, and/or as a common logical channel that may be used by more thanone wireless device (e.g., a group of wireless device).

A logical channel may be defined by the type of information it carries.The set of logical channels (e.g., in an NR configuration) may compriseone or more channels described below. A paging control channel (PCCH)may comprise/carry one or more paging messages used to page a wirelessdevice whose location is not known to the network on a cell level. Abroadcast control channel (BCCH) may comprise/carry system informationmessages in the form of a master information block (MIB) and severalsystem information blocks (SIBs). The system information messages may beused by wireless devices to obtain information about how a cell isconfigured and how to operate within the cell. A common control channel(CCCH) may comprise/carry control messages together with random access.A dedicated control channel (DCCH) may comprise/carry control messagesto/from a specific wireless device to configure the wireless device withconfiguration information. A dedicated traffic channel (DTCH) maycomprise/carry user data to/from a specific wireless device.

Transport channels may be used between the MAC and PHY layers. Transportchannels may be defined by how the information they carry issent/transmitted (e.g., via an over the air interface). The set oftransport channels (e.g., that may be defined by an NR configuration orany other configuration) may comprise one or more of the followingchannels. A paging channel (PCH) may comprise/carry paging messages thatoriginated from the PCCH. A broadcast channel (BCH) may comprise/carrythe MIB from the BCCH. A downlink shared channel (DL-SCH) maycomprise/carry downlink data and signaling messages, including the SIBsfrom the BCCH. An uplink shared channel (UL-SCH) may comprise/carryuplink data and signaling messages. A random access channel (RACH) mayprovide a wireless device with an access to the network without anyprior scheduling.

The PHY layer may use physical channels to pass/transfer informationbetween processing levels of the PHY layer. A physical channel may havean associated set of time-frequency resources for carrying theinformation of one or more transport channels. The PHY layer maygenerate control information to support the low-level operation of thePHY layer. The PHY layer may provide/transfer the control information tothe lower levels of the PHY layer via physical control channels (e.g.,referred to as L1/L2 control channels). The set of physical channels andphysical control channels (e.g., that may be defined by an NRconfiguration or any other configuration) may comprise one or more ofthe following channels. A physical broadcast channel (PBCH) maycomprise/carry the MIB from the BCH. A physical downlink shared channel(PDSCH) may comprise/carry downlink data and signaling messages from theDL-SCH, as well as paging messages from the PCH. A physical downlinkcontrol channel (PDCCH) may comprise/carry downlink control information(DCI), which may comprise downlink scheduling commands, uplinkscheduling grants, and uplink power control commands A physical uplinkshared channel (PUSCH) may comprise/carry uplink data and signalingmessages from the UL-SCH and in some instances uplink controlinformation (UCI) as described below. A physical uplink control channel(PUCCH) may comprise/carry UCI, which may comprise HARQ acknowledgments,channel quality indicators (CQI), pre-coding matrix indicators (PMI),rank indicators (RI), and scheduling requests (SR). A physical randomaccess channel (PRACH) may be used for random access.

The physical layer may generate physical signals to support thelow-level operation of the physical layer, which may be similar to thephysical control channels. As shown in FIG. 5A and FIG. 5B, the physicallayer signals (e.g., that may be defined by an NR configuration or anyother configuration) may comprise primary synchronization signals (PSS),secondary synchronization signals (SSS), channel state informationreference signals (CSI-RS), demodulation reference signals (DM-RS),sounding reference signals (SRS), phase-tracking reference signals (PTRS), and/or any other signals.

One or more of the channels (e.g., logical channels, transport channels,physical channels, etc.) may be used to carry out functions associatedwith the control plan protocol stack (e.g., NR control plane protocolstack). FIG. 2B shows an example control plane configuration (e.g., anNR control plane protocol stack). As shown in FIG. 2B, the control planeconfiguration (e.g., the NR control plane protocol stack) may usesubstantially the same/similar one or more protocol layers (e.g., PHY211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224) asthe example user plane configuration (e.g., the NR user plane protocolstack). Similar four protocol layers may comprise the PHYs 211 and 221,the MACs 212 and 222, the RLCs 213 and 223, and the PDCPs 214 and 224.The control plane configuration (e.g., the NR control plane stack) mayhave radio resource controls (RRCs) 216 and 226 and NAS protocols 217and 237 at the top of the control plane configuration (e.g., the NRcontrol plane protocol stack), for example, instead of having the SDAPs215 and 225. The control plane configuration may comprise an AMF 230comprising the NAS protocol 237.

The NAS protocols 217 and 237 may provide control plane functionalitybetween the wireless device 210 and the AMF 230 (e.g., the AMF 158A orany other AMF) and/or, more generally, between the wireless device 210and a CN (e.g., the CN 152 or any other CN). The NAS protocols 217 and237 may provide control plane functionality between the wireless device210 and the AMF 230 via signaling messages, referred to as NAS messages.There may be no direct path between the wireless device 210 and the AMF230 via which the NAS messages may be transported. The NAS messages maybe transported using the AS of the Uu and NG interfaces. The NASprotocols 217 and 237 may provide control plane functionality, such asauthentication, security, a connection setup, mobility management,session management, and/or any other functionality.

The RRCs 216 and 226 may provide/configure control plane functionalitybetween the wireless device 210 and the base station 220 and/or, moregenerally, between the wireless device 210 and the RAN (e.g., the basestation 220). The RRC layers 216 and 226 may provide/configure controlplane functionality between the wireless device 210 and the base station220 via signaling messages, which may be referred to as RRC messages.The RRC messages may be transmitted between the wireless device 210 andthe RAN (e.g., the base station 220) using signaling radio bearers andthe same/similar PDCP, RLC, MAC, and PHY protocol layers. The MAC layermay multiplex control-plane and user-plane data into the same TB. TheRRC layers 216 and 226 may provide/configure control planefunctionality, such as one or more of the following functionalities:broadcast of system information related to AS and NAS; paging initiatedby the CN or the RAN; establishment, maintenance and release of an RRCconnection between the wireless device 210 and the RAN (e.g., the basestation 220); security functions including key management;establishment, configuration, maintenance and release of signaling radiobearers and data radio bearers; mobility functions; QoS managementfunctions; wireless device measurement reporting (e.g., the wirelessdevice measurement reporting) and control of the reporting; detection ofand recovery from radio link failure (RLF); and/or NAS message transfer.As part of establishing an RRC connection, RRC layers 216 and 226 mayestablish an RRC context, which may involve configuring parameters forcommunication between the wireless device 210 and the RAN (e.g., thebase station 220).

FIG. 6 shows example RRC states and RRC state transitions. An RRC stateof a wireless device may be changed to another RRC state (e.g., RRCstate transitions of a wireless device). The wireless device may besubstantially the same or similar to the wireless device 106, 210, orany other wireless device. A wireless device may be in at least one of aplurality of states, such as three RRC states comprising RRC connected602 (e.g., RRC_CONNECTED), RRC idle 606 (e.g., RRC_IDLE), and RRCinactive 604 (e.g., RRC_INACTIVE). The RRC inactive 604 may be RRCconnected but inactive.

An RRC connection may be established for the wireless device. Forexample, this may be during an RRC connected state. During the RRCconnected state (e.g., during the RRC connected 602), the wirelessdevice may have an established RRC context and may have at least one RRCconnection with a base station. The base station may be similar to oneof the one or more base stations (e.g., one or more base stations of theRAN 104 shown in FIG. 1A, one of the gNBs 160 or ng-eNBs 162 shown inFIG. 1B, the base station 220 shown in FIG. 2A and FIG. 2B, or any otherbase stations). The base station with which the wireless device isconnected (e.g., has established an RRC connection) may have the RRCcontext for the wireless device. The RRC context, which may be referredto as a wireless device context (e.g., the UE context), may compriseparameters for communication between the wireless device and the basestation. These parameters may comprise, for example, one or more of: AScontexts; radio link configuration parameters; bearer configurationinformation (e.g., relating to a data radio bearer, a signaling radiobearer, a logical channel, a QoS flow, and/or a PDU session); securityinformation; and/or layer configuration information (e.g., PHY, MAC,RLC, PDCP, and/or SDAP layer configuration information). During the RRCconnected state (e.g., the RRC connected 602), mobility of the wirelessdevice may be managed/controlled by an RAN (e.g., the RAN 104 or the NGRAN 154). The wireless device may measure received signal levels (e.g.,reference signal levels, reference signal received power, referencesignal received quality, received signal strength indicator, etc.) basedon one or more signals sent from a serving cell and neighboring cells.The wireless device may report these measurements to a serving basestation (e.g., the base station currently serving the wireless device).The serving base station of the wireless device may request a handoverto a cell of one of the neighboring base stations, for example, based onthe reported measurements. The RRC state may transition from the RRCconnected state (e.g., RRC connected 602) to an RRC idle state (e.g.,the RRC idle 606) via a connection release procedure 608. The RRC statemay transition from the RRC connected state (e.g., RRC connected 602) tothe RRC inactive state (e.g., RRC inactive 604) via a connectioninactivation procedure 610.

An RRC context may not be established for the wireless device. Forexample, this may be during the RRC idle state. During the RRC idlestate (e.g., the RRC idle 606), an RRC context may not be establishedfor the wireless device. During the RRC idle state (e.g., the RRC idle606), the wireless device may not have an RRC connection with the basestation. During the RRC idle state (e.g., the RRC idle 606), thewireless device may be in a sleep state for the majority of the time(e.g., to conserve battery power). The wireless device may wake upperiodically (e.g., once in every discontinuous reception (DRX) cycle)to monitor for paging messages (e.g., paging messages set from the RAN).Mobility of the wireless device may be managed by the wireless devicevia a procedure of a cell reselection. The RRC state may transition fromthe RRC idle state (e.g., the RRC idle 606) to the RRC connected state(e.g., the RRC connected 602) via a connection establishment procedure612, which may involve a random access procedure.

A previously established RRC context may be maintained for the wirelessdevice. For example, this may be during the RRC inactive state. Duringthe RRC inactive state (e.g., the RRC inactive 604), the RRC contextpreviously established may be maintained in the wireless device and thebase station. The maintenance of the RRC context may enable/allow a fasttransition to the RRC connected state (e.g., the RRC connected 602) withreduced signaling overhead as compared to the transition from the RRCidle state (e.g., the RRC idle 606) to the RRC connected state (e.g.,the RRC connected 602). During the RRC inactive state (e.g., the RRCinactive 604), the wireless device may be in a sleep state and mobilityof the wireless device may be managed/controlled by the wireless devicevia a cell reselection. The RRC state may transition from the RRCinactive state (e.g., the RRC inactive 604) to the RRC connected state(e.g., the RRC connected 602) via a connection resume procedure 614. TheRRC state may transition from the RRC inactive state (e.g., the RRCinactive 604) to the RRC idle state (e.g., the RRC idle 606) via aconnection release procedure 616 that may be the same as or similar toconnection release procedure 608.

An RRC state may be associated with a mobility management mechanism.During the RRC idle state (e.g., RRC idle 606) and the RRC inactivestate (e.g., the RRC inactive 604), mobility may be managed/controlledby the wireless device via a cell reselection. The purpose of mobilitymanagement during the RRC idle state (e.g., the RRC idle 606) or duringthe RRC inactive state (e.g., the RRC inactive 604) may be toenable/allow the network to be able to notify the wireless device of anevent via a paging message without having to broadcast the pagingmessage over the entire mobile communications network. The mobilitymanagement mechanism used during the RRC idle state (e.g., the RRC idle606) or during the RRC idle state (e.g., the RRC inactive 604) mayenable/allow the network to track the wireless device on a cell-grouplevel, for example, so that the paging message may be broadcast over thecells of the cell group that the wireless device currently resideswithin (e.g. instead of sending the paging message over the entiremobile communication network). The mobility management mechanisms forthe RRC idle state (e.g., the RRC idle 606) and the RRC inactive state(e.g., the RRC inactive 604) may track the wireless device on acell-group level. The mobility management mechanisms may do thetracking, for example, using different granularities of grouping. Theremay be a plurality of levels of cell-grouping granularity (e.g., threelevels of cell-grouping granularity: individual cells; cells within aRAN area identified by a RAN area identifier (RAI); and cells within agroup of RAN areas, referred to as a tracking area and identified by atracking area identifier (TAI)).

Tracking areas may be used to track the wireless device (e.g., trackingthe location of the wireless device at the CN level). The CN (e.g., theCN 102, the 5G CN 152, or any other CN) may send to the wireless devicea list of TAIs associated with a wireless device registration area(e.g., a UE registration area). A wireless device may perform aregistration update with the CN to allow the CN to update the locationof the wireless device and provide the wireless device with a new the UEregistration area, for example, if the wireless device moves (e.g., viaa cell reselection) to a cell associated with a TAI that may not beincluded in the list of TAIs associated with the UE registration area.

RAN areas may be used to track the wireless device (e.g., the locationof the wireless device at the RAN level). For a wireless device in anRRC inactive state (e.g., the RRC inactive 604), the wireless device maybe assigned/provided/configured with a RAN notification area. A RANnotification area may comprise one or more cell identities (e.g., a listof RAIs and/or a list of TAIs). A base station may belong to one or moreRAN notification areas. A cell may belong to one or more RANnotification areas. A wireless device may perform a notification areaupdate with the RAN to update the RAN notification area of the wirelessdevice, for example, if the wireless device moves (e.g., via a cellreselection) to a cell not included in the RAN notification areaassigned/provided/configured to the wireless device.

A base station storing an RRC context for a wireless device or a lastserving base station of the wireless device may be referred to as ananchor base station. An anchor base station may maintain an RRC contextfor the wireless device at least during a period of time that thewireless device stays in a RAN notification area of the anchor basestation and/or during a period of time that the wireless device stays inan RRC inactive state (e.g., RRC inactive 604).

A base station (e.g., gNBs 160 in FIG. 1B or any other base station) maybe split in two parts:

a central unit (e.g., a base station central unit, such as a gNB CU) andone or more distributed units (e.g., a base station distributed unit,such as a gNB DU). A base station central unit (CU) may be coupled toone or more base station distributed units (DUs) using an F1 interface(e.g., an F1 interface defined in an NR configuration). The base stationCU may comprise the RRC, the PDCP, and the SDAP layers. A base stationdistributed unit (DU) may comprise the RLC, the MAC, and the PHY layers.

The physical signals and physical channels (e.g., described with respectto FIG. 5A and FIG. 5B) may be mapped onto one or more symbols (e.g.,orthogonal frequency divisional multiplexing (OFDM) symbols in an NRconfiguration or any other symbols). OFDM is a multicarriercommunication scheme that transmits data over F orthogonal subcarriers(or tones). The data may be mapped to a series of complex symbols (e.g.,M-quadrature amplitude modulation (M-QAM) symbols or M-phase shiftkeying (M PSK) symbols or any other modulated symbols), referred to assource symbols, and divided into F parallel symbol streams, for example,before transmission of the data. The F parallel symbol streams may betreated as if they are in the frequency domain. The F parallel symbolsmay be used as inputs to an Inverse Fast Fourier Transform (IFFT) blockthat transforms them into the time domain. The IFFT block may take in Fsource symbols at a time, one from each of the F parallel symbolstreams. The IFFT block may use each source symbol to modulate theamplitude and phase of one of F sinusoidal basis functions thatcorrespond to the F orthogonal subcarriers. The output of the IFFT blockmay be F time-domain samples that represent the summation of the Forthogonal subcarriers. The F time-domain samples may form a single OFDMsymbol. An OFDM symbol provided/output by the IFFT block may besent/transmitted over the air interface on a carrier frequency, forexample, after one or more processes (e.g., addition of a cyclic prefix)and up-conversion. The F parallel symbol streams may be mixed, forexample, using a Fast Fourier Transform (FFT) block before beingprocessed by the IFFT block. This operation may produce Discrete FourierTransform (DFT)-precoded OFDM symbols and may be used by one or morewireless devices in the uplink to reduce the peak to average power ratio(PAPR). Inverse processing may be performed on the OFDM symbol at areceiver using an FFT block to recover the data mapped to the sourcesymbols.

FIG. 7 shows an example configuration of a frame. The frame maycomprise, for example, an NR radio frame into which OFDM symbols may begrouped. A frame (e.g., an NR radio frame) may be identified/indicatedby a system frame number (SFN) or any other value. The SFN may repeatwith a period of 1024 frames. One NR frame may be 10 milliseconds (ms)in duration and may comprise 10 subframes that are 1 ms in duration. Asubframe may be divided into one or more slots (e.g., depending onnumerologies and/or different subcarrier spacings). Each of the one ormore slots may comprise, for example, 14 OFDM symbols per slot. Anyquantity of symbols, slots, or duration may be used for any timeinterval.

The duration of a slot may depend on the numerology used for the OFDMsymbols of the slot. A flexible numerology may be supported, forexample, to accommodate different deployments (e.g., cells with carrierfrequencies below 1 GHz up to cells with carrier frequencies in themm-wave range). A flexible numerology may be supported, for example, inan NR configuration or any other radio configurations. A numerology maybe defined in terms of subcarrier spacing and/or cyclic prefix duration.Subcarrier spacings may be scaled up by powers of two from a baselinesubcarrier spacing of 15 kHz. Cyclic prefix durations may be scaled downby powers of two from a baseline cyclic prefix duration of 4.7 μs, forexample, for a numerology in an NR configuration or any other radioconfigurations. Numerologies may be defined with the followingsubcarrier spacing/cyclic prefix duration combinations: 15 kHz/4.7 μs;30 kHz/2.3 μs; 60 kHz/1.2 μs; 120 kHz/0.59 μs; 240 kHz/0.29 μs, and/orany other subcarrier spacing/cyclic prefix duration combinations.

A slot may have a fixed number/quantity of OFDM symbols (e.g., 14 OFDMsymbols). A numerology with a higher subcarrier spacing may have ashorter slot duration and more slots per subframe. Examples ofnumerology-dependent slot duration and slots-per-subframe transmissionstructure are shown in FIG. 7 (the numerology with a subcarrier spacingof 240 kHz is not shown in FIG. 7). A subframe (e.g., in an NRconfiguration) may be used as a numerology-independent time reference. Aslot may be used as the unit upon which uplink and downlinktransmissions are scheduled. Scheduling (e.g., in an NR configuration)may be decoupled from the slot duration. Scheduling may start at anyOFDM symbol. Scheduling may last for as many symbols as needed for atransmission, for example, to support low latency. These partial slottransmissions may be referred to as mini-slot or sub-slot transmissions.

FIG. 8 shows an example resource configuration of one or more carriers.The resource configuration of may comprise a slot in the time andfrequency domain for an NR carrier or any other carrier. The slot maycomprise resource elements (REs) and resource blocks (RBs). A resourceelement (RE) may be the smallest physical resource (e.g., in an NRconfiguration). An RE may span one OFDM symbol in the time domain by onesubcarrier in the frequency domain, such as shown in FIG. 8. An RB mayspan twelve consecutive REs in the frequency domain, such as shown inFIG. 8. A carrier (e.g., an NR carrier) may be limited to a width of acertain quantity of RBs and/or subcarriers (e.g., 275 RBs or 275×12=3300subcarriers). Such limitation(s), if used, may limit the carrier (e.g.,NR carrier) frequency based on subcarrier spacing (e.g., carrierfrequency of 50, 100, 200, and 400 MHz for subcarrier spacings of 15,30, 60, and 120 kHz, respectively). A 400 MHz bandwidth may be set basedon a 400 MHz per carrier bandwidth limit. Any other bandwidth may be setbased on a per carrier bandwidth limit.

A single numerology may be used across the entire bandwidth of a carrier(e.g., an NR such as shown in FIG. 8). In other example configurations,multiple numerologies may be supported on the same carrier. NR and/orother access technologies may support wide carrier bandwidths (e.g., upto 400 MHz for a subcarrier spacing of 120 kHz). Not all wirelessdevices may be able to receive the full carrier bandwidth (e.g., due tohardware limitations and/or different wireless device capabilities).Receiving and/or utilizing the full carrier bandwidth may beprohibitive, for example, in terms of wireless device power consumption.A wireless device may adapt the size of the receive bandwidth of thewireless device, for example, based on the amount of traffic thewireless device is scheduled to receive (e.g., to reduce powerconsumption and/or for other purposes). Such an adaptation may bereferred to as bandwidth adaptation.

Configuration of one or more bandwidth parts (BWPs) may support one ormore wireless devices not capable of receiving the full carrierbandwidth. BWPs may support bandwidth adaptation, for example, for suchwireless devices not capable of receiving the full carrier bandwidth. ABWP (e.g., a BWP of an NR configuration) may be defined by a subset ofcontiguous RBs on a carrier. A wireless device may be configured (e.g.,via an RRC layer) with one or more downlink BWPs per serving cell andone or more uplink BWPs per serving cell (e.g., up to four downlink BWPsper serving cell and up to four uplink BWPs per serving cell). One ormore of the configured BWPs for a serving cell may be active, forexample, at a given time. The one or more BWPs may be referred to asactive BWPs of the serving cell. A serving cell may have one or morefirst active BWPs in the uplink carrier and one or more second activeBWPs in the secondary uplink carrier, for example, if the serving cellis configured with a secondary uplink carrier.

A downlink BWP from a set of configured downlink BWPs may be linked withan uplink BWP from a set of configured uplink BWPs (e.g., for unpairedspectra). A downlink BWP and an uplink BWP may be linked, for example,if a downlink BWP index of the downlink BWP and an uplink BWP index ofthe uplink BWP are the same. A wireless device may expect that thecenter frequency for a downlink BWP is the same as the center frequencyfor an uplink BWP (e.g., for unpaired spectra).

A base station may configure a wireless device with one or more controlresource sets (CORESETs) for at least one search space. The base stationmay configure the wireless device with one or more CORESTS, for example,for a downlink BWP in a set of configured downlink BWPs on a primarycell (PCell) or on a secondary cell (SCell). A search space may comprisea set of locations in the time and frequency domains where the wirelessdevice may monitor/find/detect/identify control information. The searchspace may be a wireless device-specific search space (e.g., aUE-specific search space) or a common search space (e.g., potentiallyusable by a plurality of wireless devices or a group of wireless userdevices). A base station may configure a group of wireless devices witha common search space, on a PCell or on a primary secondary cell(PSCell), in an active downlink BWP.

A base station may configure a wireless device with one or more resourcesets for one or more PUCCH transmissions, for example, for an uplink BWPin a set of configured uplink BWPs. A wireless device may receivedownlink receptions (e.g., PDCCH or PDSCH) in a downlink BWP, forexample, according to a configured numerology (e.g., a configuredsubcarrier spacing and/or a configured cyclic prefix duration) for thedownlink BWP. The wireless device may send/transmit uplink transmissions(e.g., PUCCH or PUSCH) in an uplink BWP, for example, according to aconfigured numerology (e.g., a configured subcarrier spacing and/or aconfigured cyclic prefix length for the uplink BWP).

One or more BWP indicator fields may be provided/comprised in DownlinkControl Information (DCI). A value of a BWP indicator field may indicatewhich BWP in a set of configured BWPs is an active downlink BWP for oneor more downlink receptions. The value of the one or more BWP indicatorfields may indicate an active uplink BWP for one or more uplinktransmissions.

A base station may semi-statically configure a wireless device with adefault downlink BWP within a set of configured downlink BWPs associatedwith a PCell. A default downlink BWP may be an initial active downlinkBWP, for example, if the base station does not provide/configure adefault downlink BWP to/for the wireless device. The wireless device maydetermine which BWP is the initial active downlink BWP, for example,based on a CORESET configuration obtained using the PBCH.

A base station may configure a wireless device with a BWP inactivitytimer value for a PCell. The wireless device may start or restart a BWPinactivity timer at any appropriate time. The wireless device may startor restart the BWP inactivity timer, for example, if one or moreconditions are satisfied. The one or more conditions may comprise atleast one of: the wireless device detects DCI indicating an activedownlink BWP other than a default downlink BWP for a paired spectraoperation; the wireless device detects DCI indicating an active downlinkBWP other than a default downlink BWP for an unpaired spectra operation;and/or the wireless device detects DCI indicating an active uplink BWPother than a default uplink BWP for an unpaired spectra operation. Thewireless device may start/run the BWP inactivity timer toward expiration(e.g., increment from zero to the BWP inactivity timer value, ordecrement from the BWP inactivity timer value to zero), for example, ifthe wireless device does not detect DCI during a time interval (e.g., 1ms or 0.5 ms). The wireless device may switch from the active downlinkBWP to the default downlink BWP, for example, if the BWP inactivitytimer expires.

A base station may semi-statically configure a wireless device with oneor more BWPs. A wireless device may switch an active BWP from a firstBWP to a second BWP, for example, after or in response to receiving DCIindicating the second BWP as an active BWP. A wireless device may switchan active BWP from a first BWP to a second BWP, for example, after or inresponse to an expiry of the BWP inactivity timer (e.g., if the secondBWP is the default BWP).

A downlink BWP switching may refer to switching an active downlink BWPfrom a first downlink BWP to a second downlink BWP (e.g., the seconddownlink BWP is activated and the first downlink BWP is deactivated). Anuplink BWP switching may refer to switching an active uplink BWP from afirst uplink BWP to a second uplink BWP (e.g., the second uplink BWP isactivated and the first uplink BWP is deactivated). Downlink and uplinkBWP switching may be performed independently (e.g., in pairedspectrum/spectra). Downlink and uplink BWP switching may be performedsimultaneously (e.g., in unpaired spectrum/spectra). Switching betweenconfigured BWPs may occur, for example, based on RRC signaling, DCIsignaling, expiration of a BWP inactivity timer, and/or an initiation ofrandom access.

FIG. 9 shows an example of configured BWPs. Bandwidth adaptation usingmultiple BWPs (e.g., three configured BWPs for an NR carrier) may beavailable. A wireless device configured with multiple BWPs (e.g., thethree BWPs) may switch from one BWP to another BWP at a switching point.The BWPs may comprise: a BWP 902 having a bandwidth of 40 MHz and asubcarrier spacing of 15 kHz; a BWP 904 having a bandwidth of 10 MHz anda subcarrier spacing of 15 kHz; and a BWP 906 having a bandwidth of 20MHz and a subcarrier spacing of 60 kHz. The BWP 902 may be an initialactive BWP, and the BWP 904 may be a default BWP. The wireless devicemay switch between BWPs at switching points. The wireless device mayswitch from the BWP 902 to the BWP 904 at a switching point 908. Theswitching at the switching point 908 may occur for any suitable reasons.The switching at a switching point 908 may occur, for example, after orin response to an expiry of a BWP inactivity timer (e.g., indicatingswitching to the default BWP). The switching at the switching point 908may occur, for example, after or in response to receiving DCI indicatingBWP 904 as the active BWP. The wireless device may switch at a switchingpoint 910 from an active BWP 904 to the BWP 906, for example, after orin response receiving DCI indicating BWP 906 as a new active BWP. Thewireless device may switch at a switching point 912 from an active BWP906 to the BWP 904, for example, after or in response to an expiry of aBWP inactivity timer. The wireless device may switch at the switchingpoint 912 from an active BWP 906 to the BWP 904, for example, after orin response receiving DCI indicating BWP 904 as a new active BWP. Thewireless device may switch at a switching point 914 from an active BWP904 to the BWP 902, for example, after or in response receiving DCIindicating the BWP 902 as a new active BWP.

Wireless device procedures for switching BWPs on a secondary cell may bethe same/similar as those on a primary cell, for example, if thewireless device is configured for a secondary cell with a defaultdownlink BWP in a set of configured downlink BWPs and a timer value. Thewireless device may use the timer value and the default downlink BWP forthe secondary cell in the same/similar manner as the wireless deviceuses the timer value and/or default BWPs for a primary cell. The timervalue (e.g., the BWP inactivity timer) may be configured per cell (e.g.,for one or more BWPs), for example, via RRC signaling or any othersignaling. One or more active BWPs may switch to another BWP, forexample, based on an expiration of the BWP inactivity timer.

Two or more carriers may be aggregated and data may be simultaneouslytransmitted to/from the same wireless device using carrier aggregation(CA) (e.g., to increase data rates). The aggregated carriers in CA maybe referred to as component carriers (CCs). There may be anumber/quantity of serving cells for the wireless device (e.g., oneserving cell for a CC), for example, if CA is configured/used. The CCsmay have multiple configurations in the frequency domain.

FIG. 10A shows example CA configurations based on CCs. As shown in FIG.10A, three types of CA configurations may comprise an intraband(contiguous) configuration 1002, an intraband (non-contiguous)configuration 1004, and/or an interband configuration 1006. In theintraband (contiguous) configuration 1002, two CCs may be aggregated inthe same frequency band (frequency band A) and may be located directlyadjacent to each other within the frequency band. In the intraband(non-contiguous) configuration 1004, two CCs may be aggregated in thesame frequency band (frequency band A) but may be separated from eachother in the frequency band by a gap. In the interband configuration1006, two CCs may be located in different frequency bands (e.g.,frequency band A and frequency band B, respectively).

A network may set the maximum quantity of CCs that can be aggregated(e.g., up to 32 CCs may be aggregated in NR, or any other quantity maybe aggregated in other systems). The aggregated CCs may have the same ordifferent bandwidths, subcarrier spacing, and/or duplexing schemes (TDD,FDD, or any other duplexing schemes). A serving cell for a wirelessdevice using CA may have a downlink CC. One or more uplink CCs may beoptionally configured for a serving cell (e.g., for FDD). The ability toaggregate more downlink carriers than uplink carriers may be useful, forexample, if the wireless device has more data traffic in the downlinkthan in the uplink.

One of the aggregated cells for a wireless device may be referred to asa primary cell (PCell), for example, if a CA is configured. The PCellmay be the serving cell that the wireless initially connects to oraccess to, for example, during or at an RRC connection establishment, anRRC connection reestablishment, and/or a handover. The PCell mayprovide/configure the wireless device with NAS mobility information andthe security input. Wireless device may have different PCells. For thedownlink, the carrier corresponding to the PCell may be referred to asthe downlink primary CC (DL PCC). For the uplink, the carriercorresponding to the PCell may be referred to as the uplink primary CC(UL PCC). The other aggregated cells (e.g., associated with CCs otherthan the DL PCC and UL PCC) for the wireless device may be referred toas secondary cells (SCells). The SCells may be configured, for example,after the PCell is configured for the wireless device. An SCell may beconfigured via an RRC connection reconfiguration procedure. For thedownlink, the carrier corresponding to an SCell may be referred to as adownlink secondary CC (DL SCC). For the uplink, the carriercorresponding to the SCell may be referred to as the uplink secondary CC(UL SCC).

Configured SCells for a wireless device may be activated or deactivated,for example, based on traffic and channel conditions. Deactivation of anSCell may cause the wireless device to stop PDCCH and PDSCH reception onthe SCell and PUSCH, SRS, and CQI transmissions on the SCell. ConfiguredSCells may be activated or deactivated, for example, using a MAC CE(e.g., the MAC CE described with respect to FIG. 4B). A MAC CE may use abitmap (e.g., one bit per SCell) to indicate which SCells (e.g., in asubset of configured SCells) for the wireless device are activated ordeactivated. Configured SCells may be deactivated, for example, after orin response to an expiration of an SCell deactivation timer (e.g., oneSCell deactivation timer per SCell may be configured).

DCI may comprise control information, such as scheduling assignments andscheduling grants, for a cell. DCI may be sent/transmitted via the cellcorresponding to the scheduling assignments and/or scheduling grants,which may be referred to as a self-scheduling. DCI comprising controlinformation for a cell may be sent/transmitted via another cell, whichmay be referred to as a cross-carrier scheduling. Uplink controlinformation (UCI) may comprise control information, such as HARQacknowledgments and channel state feedback (e.g., CQI, PMI, and/or RI)for aggregated cells. UCI may be transmitted via an uplink controlchannel (e.g., a PUCCH) of the PCell or a certain SCell (e.g., an SCellconfigured with PUCCH). For a larger number of aggregated downlink CCs,the PUCCH of the PCell may become overloaded. Cells may be divided intomultiple PUCCH groups.

FIG. 10B shows example group of cells. Aggregated cells may beconfigured into one or more PUCCH groups (e.g., as shown in FIG. 10B).One or more cell groups or one or more uplink control channel groups(e.g., a PUCCH group 1010 and a PUCCH group 1050) may comprise one ormore downlink CCs, respectively. The PUCCH group 1010 may comprise oneor more downlink CCs, for example, three downlink CCs: a PCell 1011(e.g., a DL PCC), an SCell 1012 (e.g., a DL SCC), and an SCell 1013(e.g., a DL SCC). The PUCCH group 1050 may comprise one or more downlinkCCs, for example, three downlink CCs: a PUCCH SCell (or PSCell) 1051(e.g., a DL SCC), an SCell 1052 (e.g., a DL SCC), and an SCell 1053(e.g., a DL SCC). One or more uplink CCs of the PUCCH group 1010 may beconfigured as a PCell 1021 (e.g., a UL PCC), an SCell 1022 (e.g., a ULSCC), and an SCell 1023 (e.g., a UL SCC). One or more uplink CCs of thePUCCH group 1050 may be configured as a PUCCH SCell (or PSCell) 1061(e.g., a UL SCC), an SCell 1062 (e.g., a UL SCC), and an SCell 1063(e.g., a UL SCC). UCI related to the downlink CCs of the PUCCH group1010, shown as UCI 1031, UCI 1032, and UCI 1033, may be transmitted viathe uplink of the PCell 1021 (e.g., via the PUCCH of the PCell 1021).UCI related to the downlink CCs of the PUCCH group 1050, shown as UCI1071, UCI 1072, and UCI 1073, may be sent/transmitted via the uplink ofthe PUCCH SCell (or PSCell) 1061 (e.g., via the PUCCH of the PUCCH SCell1061). A single uplink PCell may be configured to send/transmit UCIrelating to the six downlink CCs, for example, if the aggregated cellsshown in FIG. 10B are not divided into the PUCCH group 1010 and thePUCCH group 1050. The PCell 1021 may become overloaded, for example, ifthe UCIs 1031, 1032, 1033, 1071, 1072, and 1073 are sent/transmitted viathe PCell 1021. By dividing transmissions of UCI between the PCell 1021and the PUCCH SCell (or PSCell) 1061, overloading may be preventedand/or reduced.

A PCell may comprise a downlink carrier (e.g., the PCell 1011) and anuplink carrier (e.g., the PCell 1021). An SCell may comprise only adownlink carrier. A cell, comprising a downlink carrier and optionallyan uplink carrier, may be assigned with a physical cell ID and a cellindex. The physical cell ID or the cell index may indicate/identify adownlink carrier and/or an uplink carrier of the cell, for example,depending on the context in which the physical cell ID is used. Aphysical cell ID may be determined, for example, using a synchronizationsignal (e.g., PSS and/or SSS) transmitted via a downlink componentcarrier. A cell index may be determined, for example, using one or moreRRC messages. A physical cell ID may be referred to as a carrier ID, anda cell index may be referred to as a carrier index. A first physicalcell ID for a first downlink carrier may refer to the first physicalcell ID for a cell comprising the first downlink carrier. Substantiallythe same/similar concept may apply to, for example, a carrieractivation. Activation of a first carrier may refer to activation of acell comprising the first carrier.

A multi-carrier nature of a PHY layer may be exposed/indicated to a MAClayer (e.g., in a CA configuration). A HARQ entity may operate on aserving cell. A transport block may be generated per assignment/grantper serving cell. A transport block and potential HARQ retransmissionsof the transport block may be mapped to a serving cell.

For the downlink, a base station may send/transmit (e.g., unicast,multicast, and/or broadcast), to one or more wireless devices, one ormore reference signals (RSs) (e.g., PSS, SSS, CSI-RS, DM-RS, and/orPT-RS). For the uplink, the one or more wireless devices maysend/transmit one or more RSs to the base station (e.g., DM-RS, PT-RS,and/or SRS). The PSS and the SSS may be sent/transmitted by the basestation and used by the one or more wireless devices to synchronize theone or more wireless devices with the base station. A synchronizationsignal (SS)/physical broadcast channel (PBCH) block may comprise thePSS, the SSS, and the PBCH. The base station may periodicallysend/transmit a burst of SS/PBCH blocks, which may be referred to asSSBs.

FIG. 11A shows an example mapping of one or more SS/PBCH blocks. A burstof SS/PBCH blocks may comprise one or more SS/PBCH blocks (e.g., 4SS/PBCH blocks, as shown in FIG. 11A). Bursts may be sent/transmittedperiodically (e.g., every 2 frames, 20 ms, or any other durations). Aburst may be restricted to a half-frame (e.g., a first half-frame havinga duration of 5 ms). Such parameters (e.g., the number of SS/PBCH blocksper burst, periodicity of bursts, position of the burst within theframe) may be configured, for example, based on at least one of: acarrier frequency of a cell in which the SS/PBCH block issent/transmitted; a numerology or subcarrier spacing of the cell; aconfiguration by the network (e.g., using RRC signaling); and/or anyother suitable factor(s). A wireless device may assume a subcarrierspacing for the SS/PBCH block based on the carrier frequency beingmonitored, for example, unless the radio network configured the wirelessdevice to assume a different subcarrier spacing.

The SS/PBCH block may span one or more OFDM symbols in the time domain(e.g., 4 OFDM symbols, as shown in FIG. 11A or any other quantity/numberof symbols) and may span one or more subcarriers in the frequency domain(e.g., 240 contiguous subcarriers or any other quantity/number ofsubcarriers). The PSS, the SSS, and the PBCH may have a common centerfrequency. The PSS may be sent/transmitted first and may span, forexample, 1 OFDM symbol and 127 subcarriers. The SSS may besent/transmitted after the PSS (e.g., two symbols later) and may span 1OFDM symbol and 127 subcarriers. The PBCH may be sent/transmitted afterthe PSS (e.g., across the next 3 OFDM symbols) and may span 240subcarriers (e.g., in the second and fourth OFDM symbols as shown inFIG. 11A) and/or may span fewer than 240 subcarriers (e.g., in the thirdOFDM symbols as shown in FIG. 11A).

The location of the SS/PBCH block in the time and frequency domains maynot be known to the wireless device (e.g., if the wireless device issearching for the cell). The wireless device may monitor a carrier forthe PSS, for example, to find and select the cell. The wireless devicemay monitor a frequency location within the carrier. The wireless devicemay search for the PSS at a different frequency location within thecarrier, for example, if the PSS is not found after a certain duration(e.g., 20 ms). The wireless device may search for the PSS at a differentfrequency location within the carrier, for example, as indicated by asynchronization raster. The wireless device may determine the locationsof the SSS and the PBCH, respectively, for example, based on a knownstructure of the SS/PBCH block if the PSS is found at a location in thetime and frequency domains. The SS/PBCH block may be a cell-defining SSblock (CD-SSB). A primary cell may be associated with a CD-SSB. TheCD-SSB may be located on a synchronization raster. A cellselection/search and/or reselection may be based on the CD-SSB.

The SS/PBCH block may be used by the wireless device to determine one ormore parameters of the cell. The wireless device may determine aphysical cell identifier (PCI) of the cell, for example, based on thesequences of the PSS and the SSS, respectively. The wireless device maydetermine a location of a frame boundary of the cell, for example, basedon the location of the SS/PBCH block. The SS/PBCH block may indicatethat it has been sent/transmitted in accordance with a transmissionpattern. An SS/PBCH block in the transmission pattern may be a knowndistance from the frame boundary (e.g., a predefined distance for a RANconfiguration among one or more networks, one or more base stations, andone or more wireless devices).

The PBCH may use a QPSK modulation and/or forward error correction(FEC). The FEC may use polar coding. One or more symbols spanned by thePBCH may comprise/carry one or more DM-RSs for demodulation of the PBCH.The PBCH may comprise an indication of a current system frame number(SFN) of the cell and/or a SS/PBCH block timing index. These parametersmay facilitate time synchronization of the wireless device to the basestation. The PBCH may comprise a MIB used to send/transmit to thewireless device one or more parameters. The MIB may be used by thewireless device to locate remaining minimum system information (RMSI)associated with the cell. The RMSI may comprise a System InformationBlock Type 1 (SIB1). The SIB1 may comprise information for the wirelessdevice to access the cell. The wireless device may use one or moreparameters of the MIB to monitor a PDCCH, which may be used to schedulea PDSCH. The PDSCH may comprise the SIB1. The SIB1 may be decoded usingparameters provided/comprised in the MIB. The PBCH may indicate anabsence of SIB1. The wireless device may be pointed to a frequency, forexample, based on the PBCH indicating the absence of SIB1. The wirelessdevice may search for an SS/PBCH block at the frequency to which thewireless device is pointed.

The wireless device may assume that one or more SS/PBCH blockssent/transmitted with a same SS/PBCH block index are quasi co-located(QCLed) (e.g., having substantially the same/similar Doppler spread,Doppler shift, average gain, average delay, and/or spatial Rxparameters). The wireless device may not assume QCL for SS/PBCH blocktransmissions having different SS/PBCH block indices. SS/PBCH blocks(e.g., those within a half-frame) may be sent/transmitted in spatialdirections (e.g., using different beams that span a coverage area of thecell). A first SS/PBCH block may be sent/transmitted in a first spatialdirection using a first beam, a second SS/PBCH block may besent/transmitted in a second spatial direction using a second beam, athird SS/PBCH block may be sent/transmitted in a third spatial directionusing a third beam, a fourth SS/PBCH block may be sent/transmitted in afourth spatial direction using a fourth beam, etc.

A base station may send/transmit a plurality of SS/PBCH blocks, forexample, within a frequency span of a carrier. A first PCI of a firstSS/PBCH block of the plurality of SS/PBCH blocks may be different from asecond PCI of a second SS/PBCH block of the plurality of SS/PBCH blocks.The PCIs of SS/PBCH blocks sent/transmitted in different frequencylocations may be different or substantially the same.

The CSI-RS may be sent/transmitted by the base station and used by thewireless device to acquire/obtain/determine channel state information(CSI). The base station may configure the wireless device with one ormore CSI-RSs for channel estimation or any other suitable purpose. Thebase station may configure a wireless device with one or more of thesame/similar CSI-RSs. The wireless device may measure the one or moreCSI-RSs. The wireless device may estimate a downlink channel stateand/or generate a CSI report, for example, based on the measuring of theone or more downlink CSI-RSs. The wireless device may send/transmit theCSI report to the base station (e.g., based on periodic CSI reporting,semi-persistent CSI reporting, and/or aperiodic CSI reporting). The basestation may use feedback provided by the wireless device (e.g., theestimated downlink channel state) to perform a link adaptation.

The base station may semi-statically configure the wireless device withone or more CSI-RS resource sets. A CSI-RS resource may be associatedwith a location in the time and frequency domains and a periodicity. Thebase station may selectively activate and/or deactivate a CSI-RSresource. The base station may indicate to the wireless device that aCSI-RS resource in the CSI-RS resource set is activated and/ordeactivated.

The base station may configure the wireless device to report CSImeasurements. The base station may configure the wireless device toprovide CSI reports periodically, aperiodically, or semi-persistently.For periodic CSI reporting, the wireless device may be configured with atiming and/or periodicity of a plurality of CSI reports. For aperiodicCSI reporting, the base station may request a CSI report. The basestation may command the wireless device to measure a configured CSI-RSresource and provide a CSI report relating to the measurement(s). Forsemi-persistent CSI reporting, the base station may configure thewireless device to send/transmit periodically, and selectively activateor deactivate the periodic reporting (e.g., via one or moreactivation/deactivation MAC CEs and/or one or more DCIs). The basestation may configure the wireless device with a CSI-RS resource set andCSI reports, for example, using RRC signaling.

The CSI-RS configuration may comprise one or more parameters indicating,for example, up to 32 antenna ports (or any other quantity of antennaports). The wireless device may be configured to use/employ the sameOFDM symbols for a downlink CSI-RS and a CORESET, for example, if thedownlink CSI-RS and CORESET are spatially QCLed and resource elementsassociated with the downlink CSI-RS are outside of the physical resourceblocks (PRBs) configured for the CORESET. The wireless device may beconfigured to use/employ the same OFDM symbols for a downlink CSI-RS andSS/PBCH blocks, for example, if the downlink CSI-RS and SS/PBCH blocksare spatially QCLed and resource elements associated with the downlinkCSI-RS are outside of PRBs configured for the SS/PBCH blocks.

Downlink DM-RSs may be sent/transmitted by a base station andreceived/used by a wireless device for a channel estimation. Thedownlink DM-RSs may be used for coherent demodulation of one or moredownlink physical channels (e.g., PDSCH). A network (e.g., an NRnetwork) may support one or more variable and/or configurable DM-RSpatterns for data demodulation. At least one downlink DM-RSconfiguration may support a front-loaded DM-RS pattern. A front-loadedDM-RS may be mapped over one or more OFDM symbols (e.g., one or twoadjacent OFDM symbols). A base station may semi-statically configure thewireless device with a number/quantity (e.g. a maximum number/quantity)of front-loaded DM-RS symbols for a PDSCH. A DM-RS configuration maysupport one or more DM-RS ports. A DM-RS configuration may support up toeight orthogonal downlink DM-RS ports per wireless device (e.g., forsingle user-MIMO). A DM-RS configuration may support up to 4 orthogonaldownlink DM-RS ports per wireless device (e.g., for multiuser-MIMO). Aradio network may support (e.g., at least for CP-OFDM) a common DM-RSstructure for downlink and uplink. A DM-RS location, a DM-RS pattern,and/or a scrambling sequence may be the same or different. The basestation may send/transmit a downlink DM-RS and a corresponding PDSCH,for example, using the same precoding matrix. The wireless device mayuse the one or more downlink DM-RSs for coherent demodulation/channelestimation of the PDSCH.

A transmitter (e.g., a transmitter of a base station) may use a precodermatrices for a part of a transmission bandwidth. The transmitter may usea first precoder matrix for a first bandwidth and a second precodermatrix for a second bandwidth. The first precoder matrix and the secondprecoder matrix may be different, for example, based on the firstbandwidth being different from the second bandwidth. The wireless devicemay assume that a same precoding matrix is used across a set of PRBs.The set of PRBs may be determined/indicated/identified/denoted as aprecoding resource block group (PRG).

A PDSCH may comprise one or more layers. The wireless device may assumethat at least one symbol with DM-RS is present on a layer of the one ormore layers of the PDSCH. A higher layer may configure one or moreDM-RSs for a PDSCH (e.g., up to 3 DMRSs for the PDSCH). Downlink PT-RSmay be sent/transmitted by a base station and used by a wireless device,for example, for a phase-noise compensation. Whether a downlink PT-RS ispresent or not may depend on an RRC configuration. The presence and/orthe pattern of the downlink PT-RS may be configured on a wirelessdevice-specific basis, for example, using a combination of RRC signalingand/or an association with one or more parameters used/employed forother purposes (e.g., modulation and coding scheme (MCS)), which may beindicated by DCI. A dynamic presence of a downlink PT-RS, if configured,may be associated with one or more DCI parameters comprising at leastMCS. A network (e.g., an NR network) may support a plurality of PT-RSdensities defined in the time and/or frequency domains. A frequencydomain density (if configured/present) may be associated with at leastone configuration of a scheduled bandwidth. The wireless device mayassume a same precoding for a DM-RS port and a PT-RS port. Thequantity/number of PT-RS ports may be fewer than the quantity/number ofDM-RS ports in a scheduled resource. Downlink PT-RS may beconfigured/allocated/confined in the scheduled time/frequency durationfor the wireless device. Downlink PT-RS may be sent/transmitted viasymbols, for example, to facilitate a phase tracking at the receiver.

The wireless device may send/transmit an uplink DM-RS to a base station,for example, for a channel estimation. The base station may use theuplink DM-RS for coherent demodulation of one or more uplink physicalchannels. The wireless device may send/transmit an uplink DM-RS with aPUSCH and/or a PUCCH. The uplink DM-RS may span a range of frequenciesthat is similar to a range of frequencies associated with thecorresponding physical channel. The base station may configure thewireless device with one or more uplink DM-RS configurations. At leastone DM-RS configuration may support a front-loaded DM-RS pattern. Thefront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g.,one or two adjacent OFDM symbols). One or more uplink DM-RSs may beconfigured to send/transmit at one or more symbols of a PUSCH and/or aPUCCH. The base station may semi-statically configure the wirelessdevice with a number/quantity (e.g. the maximum number/quantity) offront-loaded DM-RS symbols for the PUSCH and/or the PUCCH, which thewireless device may use to schedule a single-symbol DM-RS and/or adouble-symbol DM-RS. A network (e.g., an NR network) may support (e.g.,for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM))a common DM-RS structure for downlink and uplink. A DM-RS location, aDM-RS pattern, and/or a scrambling sequence for the DM-RS may besubstantially the same or different.

A PUSCH may comprise one or more layers. A wireless device maysend/transmit at least one symbol with DM-RS present on a layer of theone or more layers of the PUSCH. A higher layer may configure one ormore DM-RSs (e.g., up to three DMRSs) for the PUSCH. Uplink PT-RS (whichmay be used by a base station for a phase tracking and/or a phase-noisecompensation) may or may not be present, for example, depending on anRRC configuration of the wireless device. The presence and/or thepattern of an uplink PT-RS may be configured on a wirelessdevice-specific basis (e.g., a UE-specific basis), for example, by acombination of RRC signaling and/or one or more parametersconfigured/employed for other purposes (e.g., MCS), which may beindicated by DCI. A dynamic presence of an uplink PT-RS, if configured,may be associated with one or more DCI parameters comprising at leastMCS. A radio network may support a plurality of uplink PT-RS densitiesdefined in time/frequency domain. A frequency domain density (ifconfigured/present) may be associated with at least one configuration ofa scheduled bandwidth. The wireless device may assume a same precodingfor a DM-RS port and a PT-RS port. A quantity/number of PT-RS ports maybe less than a quantity/number of DM-RS ports in a scheduled resource.An uplink PT-RS may be configured/allocated/confined in the scheduledtime/frequency duration for the wireless device.

One or more SRSs may be sent/transmitted by a wireless device to a basestation, for example, for a channel state estimation to support uplinkchannel dependent scheduling and/or a link adaptation. SRSsent/transmitted by the wireless device may enable/allow a base stationto estimate an uplink channel state at one or more frequencies. Ascheduler at the base station may use/employ the estimated uplinkchannel state to assign one or more resource blocks for an uplink PUSCHtransmission for the wireless device. The base station maysemi-statically configure the wireless device with one or more SRSresource sets. For an SRS resource set, the base station may configurethe wireless device with one or more SRS resources. An SRS resource setapplicability may be configured, for example, by a higher layer (e.g.,RRC) parameter. An SRS resource in a SRS resource set of the one or moreSRS resource sets (e.g., with the same/similar time domain behavior,periodic, aperiodic, and/or the like) may be sent/transmitted at a timeinstant (e.g., simultaneously), for example, if a higher layer parameterindicates beam management. The wireless device may send/transmit one ormore SRS resources in SRS resource sets. A network (e.g., an NR network)may support aperiodic, periodic, and/or semi-persistent SRStransmissions. The wireless device may send/transmit SRS resources, forexample, based on one or more trigger types. The one or more triggertypes may comprise higher layer signaling (e.g., RRC) and/or one or moreDCI formats. At least one DCI format may be used/employed for thewireless device to select at least one of one or more configured SRSresource sets. An SRS trigger type 0 may refer to an SRS triggered basedon higher layer signaling. An SRS trigger type 1 may refer to an SRStriggered based on one or more DCI formats. The wireless device may beconfigured to send/transmit an SRS, for example, after a transmission ofa PUSCH and a corresponding uplink DM-RS if a PUSCH and an SRS aresent/transmitted in a same slot. A base station may semi-staticallyconfigure a wireless device with one or more SRS configurationparameters indicating at least one of following: a SRS resourceconfiguration identifier; a number of SRS ports; time domain behavior ofan SRS resource configuration (e.g., an indication of periodic,semi-persistent, or aperiodic SRS); slot, mini-slot, and/or subframelevel periodicity; an offset for a periodic and/or an aperiodic SRSresource; a number of OFDM symbols in an SRS resource; a starting OFDMsymbol of an SRS resource; an SRS bandwidth; a frequency hoppingbandwidth; a cyclic shift; and/or an SRS sequence ID.

An antenna port may be determined/defined such that the channel overwhich a symbol on the antenna port is conveyed can be inferred from thechannel over which another symbol on the same antenna port is conveyed.The receiver may infer/determine the channel (e.g., fading gain,multipath delay, and/or the like) for conveying a second symbol on anantenna port, from the channel for conveying a first symbol on theantenna port, for example, if the first symbol and the second symbol aresent/transmitted on the same antenna port. A first antenna port and asecond antenna port may be referred to as quasi co-located (QCLed), forexample, if one or more large-scale properties of the channel over whicha first symbol on the first antenna port is conveyed may be inferredfrom the channel over which a second symbol on a second antenna port isconveyed. The one or more large-scale properties may comprise at leastone of: a delay spread; a Doppler spread; a Doppler shift; an averagegain; an average delay; and/or spatial Receiving (Rx) parameters.

Channels that use beamforming may require beam management. Beammanagement may comprise a beam measurement, a beam selection, and/or abeam indication. A beam may be associated with one or more referencesignals. A beam may be identified by one or more beamformed referencesignals. The wireless device may perform a downlink beam measurement,for example, based on one or more downlink reference signals (e.g., aCSI-RS) and generate a beam measurement report. The wireless device mayperform the downlink beam measurement procedure, for example, after anRRC connection is set up with a base station.

FIG. 11B shows an example mapping of one or more CSI-RSs. The CSI-RSsmay be mapped in the time and frequency domains. Each rectangular blockshown in FIG. 11B may correspond to a resource block (RB) within abandwidth of a cell. A base station may send/transmit one or more RRCmessages comprising CSI-RS resource configuration parameters indicatingone or more CSI-RSs. One or more of parameters may be configured byhigher layer signaling (e.g., RRC and/or MAC signaling) for a CSI-RSresource configuration. The one or more of the parameters may compriseat least one of: a CSI-RS resource configuration identity, a number ofCSI-RS ports, a CSI-RS configuration (e.g., symbol and resource element(RE) locations in a subframe), a CSI-RS subframe configuration (e.g., asubframe location, an offset, and periodicity in a radio frame), aCSI-RS power parameter, a CSI-RS sequence parameter, a code divisionmultiplexing (CDM) type parameter, a frequency density, a transmissioncomb, quasi co-location (QCL) parameters (e.g., QCL-scramblingidentity,crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid,qcl-csi-rs-configNZPid), and/or other radio resource parameters.

One or more beams may be configured for a wireless device in a wirelessdevice-specific configuration. Three beams are shown in FIG. 11B (beam#1, beam #2, and beam #3), but more or fewer beams may be configured.Beam #1 may be allocated with CSI-RS 1101 that may be sent/transmittedin one or more subcarriers in an RB of a first symbol. Beam #2 may beallocated with CSI-RS 1102 that may be sent/transmitted in one or moresubcarriers in an RB of a second symbol. Beam #3 may be allocated withCSI-RS 1103 that may be sent/transmitted in one or more subcarriers inan RB of a third symbol. A base station may use other subcarriers in thesame RB (e.g., those that are not used to send/transmit CSI-RS 1101) totransmit another CSI-RS associated with a beam for another wirelessdevice, for example, by using frequency division multiplexing (FDM).Beams used for a wireless device may be configured such that beams forthe wireless device use symbols different from symbols used by beams ofother wireless devices, for example, by using time domain multiplexing(TDM). A wireless device may be served with beams in orthogonal symbols(e.g., no overlapping symbols), for example, by using the TDM.

CSI-RSs (e.g., CSI-RSs 1101, 1102, 1103) may be sent/transmitted by thebase station and used by the wireless device for one or moremeasurements. The wireless device may measure an RSRP of configuredCSI-RS resources. The base station may configure the wireless devicewith a reporting configuration, and the wireless device may report theRSRP measurements to a network (e.g., via one or more base stations)based on the reporting configuration. The base station may determine,based on the reported measurement results, one or more transmissionconfiguration indication (TCI) states comprising a number of referencesignals. The base station may indicate one or more TCI states to thewireless device (e.g., via RRC signaling, a MAC CE, and/or DCI). Thewireless device may receive a downlink transmission with an Rx beamdetermined based on the one or more TCI states. The wireless device mayor may not have a capability of beam correspondence. The wireless devicemay determine a spatial domain filter of a transmit (Tx) beam, forexample, based on a spatial domain filter of the corresponding Rx beam,if the wireless device has the capability of beam correspondence. Thewireless device may perform an uplink beam selection procedure todetermine the spatial domain filter of the Tx beam, for example, if thewireless device does not have the capability of beam correspondence. Thewireless device may perform the uplink beam selection procedure, forexample, based on one or more sounding reference signal (SRS) resourcesconfigured to the wireless device by the base station. The base stationmay select and indicate uplink beams for the wireless device, forexample, based on measurements of the one or more SRS resourcessent/transmitted by the wireless device.

A wireless device may determine/assess (e.g., measure) a channel qualityof one or more beam pair links, for example, in a beam managementprocedure. A beam pair link may comprise a Tx beam of a base station andan Rx beam of the wireless device. The Tx beam of the base station maysend/transmit a downlink signal, and the Rx beam of the wireless devicemay receive the downlink signal. The wireless device may send/transmit abeam measurement report, for example, based on theassessment/determination. The beam measurement report may indicate oneor more beam pair quality parameters comprising at least one of: one ormore beam identifications (e.g., a beam index, a reference signal index,or the like), an RSRP, a precoding matrix indicator (PMI), a channelquality indicator (CQI), and/or a rank indicator (RI).

FIG. 12A shows examples of downlink beam management procedures. One ormore downlink beam management procedures (e.g., downlink beam managementprocedures P1, P2, and P3) may be performed. Procedure P1 may enable ameasurement (e.g., a wireless device measurement) on Tx beams of a TRP(or multiple TRPs) (e.g., to support a selection of one or more basestation Tx beams and/or wireless device Rx beams). The Tx beams of abase station and the Rx beams of a wireless device are shown as ovals inthe top row of P1 and bottom row of P1, respectively. Beamforming (e.g.,at a TRP) may comprise a Tx beam sweep for a set of beams (e.g., thebeam sweeps shown, in the top rows of P1 and P2, as ovals rotated in acounter-clockwise direction indicated by the dashed arrows). Beamforming(e.g., at a wireless device) may comprise an Rx beam sweep for a set ofbeams (e.g., the beam sweeps shown, in the bottom rows of P1 and P3, asovals rotated in a clockwise direction indicated by the dashed arrows).Procedure P2 may be used to enable a measurement (e.g., a wirelessdevice measurement) on Tx beams of a TRP (shown, in the top row of P2,as ovals rotated in a counter-clockwise direction indicated by thedashed arrow). The wireless device and/or the base station may performprocedure P2, for example, using a smaller set of beams than the set ofbeams used in procedure P1, or using narrower beams than the beams usedin procedure P1. Procedure P2 may be referred to as a beam refinement.The wireless device may perform procedure P3 for an Rx beamdetermination, for example, by using the same Tx beam(s) of the basestation and sweeping Rx beam(s) of the wireless device.

FIG. 12B shows examples of uplink beam management procedures. One ormore uplink beam management procedures (e.g., uplink beam managementprocedures U1, U2, and U3) may be performed. Procedure U1 may be used toenable a base station to perform a measurement on Tx beams of a wirelessdevice (e.g., to support a selection of one or more Tx beams of thewireless device and/or Rx beams of the base station). The Tx beams ofthe wireless device and the Rx beams of the base station are shown asovals in the top row of U1 and bottom row of U1, respectively).Beamforming (e.g., at the wireless device) may comprise one or more beamsweeps, for example, a Tx beam sweep from a set of beams (shown, in thebottom rows of U1 and U3, as ovals rotated in a clockwise directionindicated by the dashed arrows). Beamforming (e.g., at the base station)may comprise one or more beam sweeps, for example, an Rx beam sweep froma set of beams (shown, in the top rows of U1 and U2, as ovals rotated ina counter-clockwise direction indicated by the dashed arrows). ProcedureU2 may be used to enable the base station to adjust its Rx beam, forexample, if the UE uses a fixed Tx beam. The wireless device and/or thebase station may perform procedure U2, for example, using a smaller setof beams than the set of beams used in procedure P1, or using narrowerbeams than the beams used in procedure P1. Procedure U2 may be referredto as a beam refinement. The wireless device may perform procedure U3 toadjust its Tx beam, for example, if the base station uses a fixed Rxbeam.

A wireless device may initiate/start/perform a beam failure recovery(BFR) procedure, for example, based on detecting a beam failure. Thewireless device may send/transmit a BFR request (e.g., a preamble, UCI,an SR, a MAC CE, and/or the like), for example, based on the initiatingthe BFR procedure. The wireless device may detect the beam failure, forexample, based on a determination that a quality of beam pair link(s) ofan associated control channel is unsatisfactory (e.g., having an errorrate higher than an error rate threshold, a received signal power lowerthan a received signal power threshold, an expiration of a timer, and/orthe like).

The wireless device may measure a quality of a beam pair link, forexample, using one or more reference signals (RSs) comprising one ormore SS/PBCH blocks, one or more CSI-RS resources, and/or one or moreDM-RSs. A quality of the beam pair link may be based on one or more of ablock error rate (BLER), an RSRP value, a signal to interference plusnoise ratio (SINR) value, an RSRQ value, and/or a CSI value measured onRS resources. The base station may indicate that an RS resource is QCLedwith one or more DM-RSs of a channel (e.g., a control channel, a shareddata channel, and/or the like). The RS resource and the one or moreDM-RSs of the channel may be QCLed, for example, if the channelcharacteristics (e.g., Doppler shift, Doppler spread, an average delay,delay spread, a spatial Rx parameter, fading, and/or the like) from atransmission via the RS resource to the wireless device are similar orthe same as the channel characteristics from a transmission via thechannel to the wireless device.

A network (e.g., an NR network comprising a gNB and/or an ng-eNB) and/orthe wireless device may initiate/start/perform a random accessprocedure. A wireless device in an RRC idle (e.g., an RRC_IDLE) stateand/or an RRC inactive (e.g., an RRC_INACTIVE) state mayinitiate/perform the random access procedure to request a connectionsetup to a network. The wireless device may initiate/start/perform therandom access procedure from an RRC connected (e.g., an RRC_CONNECTED)state. The wireless device may initiate/start/perform the random accessprocedure to request uplink resources (e.g., for uplink transmission ofan SR if there is no PUCCH resource available) and/oracquire/obtain/determine an uplink timing (e.g., if an uplinksynchronization status is non-synchronized). The wireless device mayinitiate/start/perform the random access procedure to request one ormore system information blocks (SIBs) (e.g., other system informationblocks, such as SIB2, SIB3, and/or the like). The wireless device mayinitiate/start/perform the random access procedure for a beam failurerecovery request. A network may initiate/start/perform a random accessprocedure, for example, for a handover and/or for establishing timealignment for an SCell addition.

FIG. 13A shows an example four-step random access procedure. Thefour-step random access procedure may comprise a four-stepcontention-based random access procedure. A base station maysend/transmit a configuration message 1310 to a wireless device, forexample, before initiating the random access procedure. The four-steprandom access procedure may comprise transmissions of four messagescomprising: a first message (e.g., Msg 1 1311), a second message (e.g.,Msg 2 1312), a third message (e.g., Msg 3 1313), and a fourth message(e.g., Msg 4 1314). The first message (e.g., Msg 1 1311) may comprise apreamble (or a random access preamble). The first message (e.g., Msg 11311) may be referred to as a preamble. The second message (e.g., Msg 21312) may comprise as a random access response (RAR). The second message(e.g., Msg 2 1312) may be referred to as an RAR.

The configuration message 1310 may be sent/transmitted, for example,using one or more RRC messages. The one or more RRC messages mayindicate one or more random access channel (RACH) parameters to thewireless device. The one or more RACH parameters may comprise at leastone of: general parameters for one or more random access procedures(e.g., RACH-configGeneral); cell-specific parameters (e.g.,RACH-ConfigCommon); and/or dedicated parameters (e.g.,RACH-configDedicated). The base station may send/transmit (e.g.,broadcast or multicast) the one or more RRC messages to one or morewireless devices. The one or more RRC messages may be wirelessdevice-specific. The one or more RRC messages that are wirelessdevice-specific may be, for example, dedicated RRC messagessent/transmitted to a wireless device in an RRC connected (e.g., anRRC_CONNECTED) state and/or in an RRC inactive (e.g., an RRC_INACTIVE)state. The wireless devices may determine, based on the one or more RACHparameters, a time-frequency resource and/or an uplink transmit powerfor transmission of the first message (e.g., Msg 1 1311) and/or thethird message (e.g., Msg 3 1313). The wireless device may determine areception timing and a downlink channel for receiving the second message(e.g., Msg 2 1312) and the fourth message (e.g., Msg 4 1314), forexample, based on the one or more RACH parameters.

The one or more RACH parameters provided/configured/comprised in theconfiguration message 1310 may indicate one or more Physical RACH(PRACH) occasions available for transmission of the first message (e.g.,Msg 1 1311). The one or more PRACH occasions may be predefined (e.g., bya network comprising one or more base stations). The one or more RACHparameters may indicate one or more available sets of one or more PRACHoccasions (e.g., prach-ConfigIndex). The one or more RACH parameters mayindicate an association between (a) one or more PRACH occasions and (b)one or more reference signals. The one or more RACH parameters mayindicate an association between (a) one or more preambles and (b) one ormore reference signals. The one or more reference signals may be SS/PBCHblocks and/or CSI-RSs. The one or more RACH parameters may indicate aquantity/number of SS/PBCH blocks mapped to a PRACH occasion and/or aquantity/number of preambles mapped to a SS/PBCH blocks.

The one or more RACH parameters provided/configured/comprised in theconfiguration message 1310 may be used to determine an uplink transmitpower of first message (e.g., Msg 1 1311) and/or third message (e.g.,Msg 3 1313). The one or more RACH parameters may indicate a referencepower for a preamble transmission (e.g., a received target power and/oran initial power of the preamble transmission). There may be one or morepower offsets indicated by the one or more RACH parameters. The one ormore RACH parameters may indicate: a power ramping step; a power offsetbetween SSB and CSI-RS; a power offset between transmissions of thefirst message (e.g., Msg 1 1311) and the third message (e.g., Msg 31313); and/or a power offset value between preamble groups. The one ormore RACH parameters may indicate one or more thresholds, for example,based on which the wireless device may determine at least one referencesignal (e.g., an SSB and/or CSI-RS) and/or an uplink carrier (e.g., anormal uplink (NUL) carrier and/or a supplemental uplink (SUL) carrier).

The first message (e.g., Msg 1 1311) may comprise one or more preambletransmissions (e.g., a preamble transmission and one or more preambleretransmissions). An RRC message may be used to configure one or morepreamble groups (e.g., group A and/or group B). A preamble group maycomprise one or more preambles. The wireless device may determine thepreamble group, for example, based on a pathloss measurement and/or asize of the third message (e.g., Msg 3 1313). The wireless device maymeasure an RSRP of one or more reference signals (e.g., SSBs and/orCSI-RSs) and determine at least one reference signal having an RSRPabove an RSRP threshold (e.g., rsrp-ThresholdSSB and/orrsrp-ThresholdCSI-RS). The wireless device may select at least onepreamble associated with the one or more reference signals and/or aselected preamble group, for example, if the association between the oneor more preambles and the at least one reference signal is configured byan RRC message.

The wireless device may determine the preamble, for example, based onthe one or more RACH parameters provided/configured/comprised in theconfiguration message 1310. The wireless device may determine thepreamble, for example, based on a pathloss measurement, an RSRPmeasurement, and/or a size of the third message (e.g., Msg 3 1313). Theone or more RACH parameters may indicate: a preamble format; a maximumquantity/number of preamble transmissions; and/or one or more thresholdsfor determining one or more preamble groups (e.g., group A and group B).A base station may use the one or more RACH parameters to configure thewireless device with an association between one or more preambles andone or more reference signals (e.g., SSBs and/or CSI-RSs). The wirelessdevice may determine the preamble to be comprised in first message(e.g., Msg 1 1311), for example, based on the association if theassociation is configured. The first message (e.g., Msg 1 1311) may besent/transmitted to the base station via one or more PRACH occasions.The wireless device may use one or more reference signals (e.g., SSBsand/or CSI-RSs) for selection of the preamble and for determining of thePRACH occasion. One or more RACH parameters (e.g.,ra-ssb-OccasionMskIndex and/or ra-OccasionList) may indicate anassociation between the PRACH occasions and the one or more referencesignals.

The wireless device may perform a preamble retransmission, for example,if no response is received after or in response to a preambletransmission (e.g., for a period of time, such as a monitoring windowfor monitoring an RAR). The wireless device may increase an uplinktransmit power for the preamble retransmission. The wireless device mayselect an initial preamble transmit power, for example, based on apathloss measurement and/or a target received preamble power configuredby the network. The wireless device may determine to resend/retransmit apreamble and may ramp up the uplink transmit power. The wireless devicemay receive one or more RACH parameters (e.g.,PREAMBLE_POWER_RAMPING_STEP) indicating a ramping step for the preambleretransmission. The ramping step may be an amount of incrementalincrease in uplink transmit power for a retransmission. The wirelessdevice may ramp up the uplink transmit power, for example, if thewireless device determines a reference signal (e.g., SSB and/or CSI-RS)that is the same as a previous preamble transmission. The wirelessdevice may count the quantity/number of preamble transmissions and/orretransmissions, for example, using a counter parameter (e.g.,PREAMBLE_TRANSMISSION_COUNTER). The wireless device may determine that arandom access procedure has been completed unsuccessfully, for example,if the quantity/number of preamble transmissions exceeds a thresholdconfigured by the one or more RACH parameters (e.g., preambleTransMax)without receiving a successful response (e.g., an RAR).

The second message (e.g., Msg 2 1312) (e.g., received by the wirelessdevice) may comprise an RAR. The second message (e.g., Msg 2 1312) maycomprise multiple RARs corresponding to multiple wireless devices. Thesecond message (e.g., Msg 2 1312) may be received, for example, after orin response to the transmitting of the first message (e.g., Msg 1 1311).The second message (e.g., Msg 2 1312) may be scheduled on the DL-SCH andmay be indicated by a PDCCH, for example, using a random access radionetwork temporary identifier (RA RNTI). The second message (e.g., Msg 21312) may indicate that the first message (e.g., Msg 1 1311) wasreceived by the base station. The second message (e.g., Msg 2 1312) maycomprise a time-alignment command that may be used by the wirelessdevice to adjust the transmission timing of the wireless device, ascheduling grant for transmission of the third message (e.g., Msg 31313), and/or a Temporary Cell RNTI (TC-RNTI). The wireless device maydetermine/start a time window (e.g., ra-ResponseWindow) to monitor aPDCCH for the second message (e.g., Msg 2 1312), for example, aftertransmitting the first message (e.g., Msg 1 1311) (e.g., a preamble).The wireless device may determine the start time of the time window, forexample, based on a PRACH occasion that the wireless device uses tosend/transmit the first message (e.g., Msg 1 1311) (e.g., the preamble).The wireless device may start the time window one or more symbols afterthe last symbol of the first message (e.g., Msg 1 1311) comprising thepreamble (e.g., the symbol in which the first message (e.g., Msg 1 1311)comprising the preamble transmission was completed or at a first PDCCHoccasion from an end of a preamble transmission). The one or moresymbols may be determined based on a numerology. The PDCCH may be mappedin a common search space (e.g., a Type1-PDCCH common search space)configured by an RRC message. The wireless device may identify/determinethe RAR, for example, based on an RNTI. Radio network temporaryidentifiers (RNTIs) may be used depending on one or more eventsinitiating/starting the random access procedure. The wireless device mayuse a RA-RNTI, for example, for one or more communications associatedwith random access or any other purpose. The RA-RNTI may be associatedwith PRACH occasions in which the wireless device sends/transmits apreamble. The wireless device may determine the RA-RNTI, for example,based on at least one of: an OFDM symbol index; a slot index; afrequency domain index; and/or a UL carrier indicator of the PRACHoccasions. An example RA-RNTI may be determined as follows:

RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id

where s_id may be an index of a first OFDM symbol of the PRACH occasion(e.g., 0≤s_id<14), t_id may be an index of a first slot of the PRACHoccasion in a system frame (e.g., 0≤t_id<80), f_id may be an index ofthe PRACH occasion in the frequency domain (e.g., 0≤f_id<8), andul_carrier_id may be a UL carrier used for a preamble transmission(e.g., 0 for an NUL carrier, and 1 for an SUL carrier).

The wireless device may send/transmit the third message (e.g., Msg 31313), for example, after or in response to a successful reception ofthe second message (e.g., Msg 2 1312) (e.g., using resources identifiedin the Msg 2 1312). The third message (e.g., Msg 3 1313) may be used,for example, for contention resolution in the contention-based randomaccess procedure. A plurality of wireless devices may send/transmit thesame preamble to a base station, and the base station may send/transmitan RAR that corresponds to a wireless device. Collisions may occur, forexample, if the plurality of wireless device interpret the RAR ascorresponding to themselves. Contention resolution (e.g., using thethird message (e.g., Msg 3 1313) and the fourth message (e.g., Msg 41314)) may be used to increase the likelihood that the wireless devicedoes not incorrectly use an identity of another the wireless device. Thewireless device may comprise a device identifier in the third message(e.g., Msg 3 1313) (e.g., a C-RNTI if assigned, a TC RNTI comprised inthe second message (e.g., Msg 2 1312), and/or any other suitableidentifier), for example, to perform contention resolution.

The fourth message (e.g., Msg 4 1314) may be received, for example,after or in response to the transmitting of the third message (e.g., Msg3 1313). The base station may address the wireless on the PDCCH (e.g.,the base station may send the PDCCH to the wireless device) using aC-RNTI, for example, If the C-RNTI was included in the third message(e.g., Msg 3 1313). The random access procedure may be determined to besuccessfully completed, for example, if the unique C RNTI of thewireless device is detected on the PDCCH (e.g., the PDCCH is scrambledby the C-RNTI). fourth message (e.g., Msg 4 1314) may be received usinga DL-SCH associated with a TC RNTI, for example, if the TC RNTI iscomprised in the third message (e.g., Msg 3 1313) (e.g., if the wirelessdevice is in an RRC idle (e.g., an RRC_IDLE) state or not otherwiseconnected to the base station). The wireless device may determine thatthe contention resolution is successful and/or the wireless device maydetermine that the random access procedure is successfully completed,for example, if a MAC PDU is successfully decoded and a MAC PDUcomprises the wireless device contention resolution identity MAC CE thatmatches or otherwise corresponds with the CCCH SDU sent/transmitted inthird message (e.g., Msg 3 1313).

The wireless device may be configured with an SUL carrier and/or an NULcarrier. An initial access (e.g., random access) may be supported via anuplink carrier. A base station may configure the wireless device withmultiple RACH configurations (e.g., two separate RACH configurationscomprising: one for an SUL carrier and the other for an NUL carrier).For random access in a cell configured with an SUL carrier, the networkmay indicate which carrier to use (NUL or SUL). The wireless device maydetermine to use the SUL carrier, for example, if a measured quality ofone or more reference signals (e.g., one or more reference signalsassociated with the NUL carrier) is lower than a broadcast threshold.Uplink transmissions of the random access procedure (e.g., the firstmessage (e.g., Msg 1 1311) and/or the third message (e.g., Msg 3 1313))may remain on, or may be performed via, the selected carrier. Thewireless device may switch an uplink carrier during the random accessprocedure (e.g., between the Msg 1 1311 and the Msg 3 1313). Thewireless device may determine and/or switch an uplink carrier for thefirst message (e.g., Msg 1 1311) and/or the third message (e.g., Msg 31313), for example, based on a channel clear assessment (e.g., alisten-before-talk).

FIG. 13B shows a two-step random access procedure. The two-step randomaccess procedure may comprise a two-step contention-free random accessprocedure. Similar to the four-step contention-based random accessprocedure, a base station may, prior to initiation of the procedure,send/transmit a configuration message 1320 to the wireless device. Theconfiguration message 1320 may be analogous in some respects to theconfiguration message 1310. The procedure shown in FIG. 13B may comprisetransmissions of two messages: a first message (e.g., Msg 1 1321) and asecond message (e.g., Msg 2 1322). The first message (e.g., Msg 1 1321)and the second message (e.g., Msg 2 1322) may be analogous in somerespects to the first message (e.g., Msg 1 1311) and a second message(e.g., Msg 2 1312), respectively. The two-step contention-free randomaccess procedure may not comprise messages analogous to the thirdmessage (e.g., Msg 3 1313) and/or the fourth message (e.g., Msg 4 1314).

The two-step (e.g., contention-free) random access procedure may beconfigured/initiated for a beam failure recovery, other SI request, anSCell addition, and/or a handover. A base station may indicate, orassign to, the wireless device a preamble to be used for the firstmessage (e.g., Msg 1 1321). The wireless device may receive, from thebase station via a PDCCH and/or an RRC, an indication of the preamble(e.g., ra-PreambleIndex).

The wireless device may start a time window (e.g., ra-ResponseWindow) tomonitor a PDCCH for the RAR, for example, after or in response tosending/transmitting the preamble. The base station may configure thewireless device with one or more beam failure recovery parameters, suchas a separate time window and/or a separate PDCCH in a search spaceindicated by an RRC message (e.g., recoverySearchSpaceId). The basestation may configure the one or more beam failure recovery parameters,for example, in association with a beam failure recovery request. Theseparate time window for monitoring the PDCCH and/or an RAR may beconfigured to start after transmitting a beam failure recovery request(e.g., the window may start any quantity of symbols and/or slots aftertransmitting the beam failure recovery request). The wireless device maymonitor for a PDCCH transmission addressed to a Cell RNTI (C-RNTI) onthe search space. During the two-step (e.g., contention-free) randomaccess procedure, the wireless device may determine that a random accessprocedure is successful, for example, after or in response totransmitting first message (e.g., Msg 1 1321) and receiving acorresponding second message (e.g., Msg 2 1322). The wireless device maydetermine that a random access procedure has successfully beencompleted, for example, if a PDCCH transmission is addressed to acorresponding C-RNTI. The wireless device may determine that a randomaccess procedure has successfully been completed, for example, if thewireless device receives an RAR comprising a preamble identifiercorresponding to a preamble sent/transmitted by the wireless deviceand/or the RAR comprises a MAC sub-PDU with the preamble identifier. Thewireless device may determine the response as an indication of anacknowledgement for an SI request.

FIG. 13C shows an example two-step random access procedure. Similar tothe random access procedures shown in FIGS. 13A and 13B, a base stationmay, prior to initiation of the procedure, send/transmit a configurationmessage 1330 to the wireless device. The configuration message 1330 maybe analogous in some respects to the configuration message 1310 and/orthe configuration message 1320. The procedure shown in FIG. 13C maycomprise transmissions of multiple messages (e.g., two messagescomprising: a first message (e.g., Msg A 1331) and a second message(e.g., Msg B 1332)).

Msg A 1320 may be sent/transmitted in an uplink transmission by thewireless device. Msg A 1320 may comprise one or more transmissions of apreamble 1341 and/or one or more transmissions of a transport block1342. The transport block 1342 may comprise contents that are similarand/or equivalent to the contents of the third message (e.g., Msg 31313) (e.g., shown in FIG. 13A). The transport block 1342 may compriseUCI (e.g., an SR, a HARQ ACK/NACK, and/or the like). The wireless devicemay receive the second message (e.g., Msg B 1332), for example, after orin response to transmitting the first message (e.g., Msg A 1331). Thesecond message (e.g., Msg B 1332) may comprise contents that are similarand/or equivalent to the contents of the second message (e.g., Msg 21312) (e.g., an RAR shown in FIG. 13A), the contents of the secondmessage (e.g., Msg 2 1322) (e.g., an RAR shown in FIG. 13B) and/or thefourth message (e.g., Msg 4 1314) (e.g., shown in FIG. 13A).

The wireless device may start/initiate the two-step random accessprocedure (e.g., the two-step random access procedure shown in FIG. 13C)for a licensed spectrum and/or an unlicensed spectrum. The wirelessdevice may determine, based on one or more factors, whether tostart/initiate the two-step random access procedure. The one or morefactors may comprise at least one of: a radio access technology in use(e.g., LTE, NR, and/or the like); whether the wireless device has avalid TA or not; a cell size; the RRC state of the wireless device; atype of spectrum (e.g., licensed vs. unlicensed); and/or any othersuitable factors.

The wireless device may determine, based on two-step RACH parameterscomprised in the configuration message 1330, a radio resource and/or anuplink transmit power for the preamble 1341 and/or the transport block1342 (e.g., comprised in the first message (e.g., Msg A 1331)). The RACHparameters may indicate an MCS, a time-frequency resource, and/or apower control for the preamble 1341 and/or the transport block 1342. Atime-frequency resource for transmission of the preamble 1341 (e.g., aPRACH) and a time-frequency resource for transmission of the transportblock 1342 (e.g., a PUSCH) may be multiplexed using FDM, TDM, and/orCDM. The RACH parameters may enable the wireless device to determine areception timing and a downlink channel for monitoring for and/orreceiving second message (e.g., Msg B 1332).

The transport block 1342 may comprise data (e.g., delay-sensitive data),an identifier of the wireless device, security information, and/ordevice information (e.g., an International Mobile Subscriber Identity(IMSI)). The base station may send/transmit the second message (e.g.,Msg B 1332) as a response to the first message (e.g., Msg A 1331). Thesecond message (e.g., Msg B 1332) may comprise at least one of: apreamble identifier; a timing advance command; a power control command;an uplink grant (e.g., a radio resource assignment and/or an MCS); awireless device identifier (e.g., a UE identifier for contentionresolution); and/or an RNTI (e.g., a C-RNTI or a TC-RNTI). The wirelessdevice may determine that the two-step random access procedure issuccessfully completed, for example, if a preamble identifier in thesecond message (e.g., Msg B 1332) corresponds to, or is matched to, apreamble sent/transmitted by the wireless device and/or the identifierof the wireless device in second message (e.g., Msg B 1332) correspondsto, or is matched to, the identifier of the wireless device in the firstmessage (e.g., Msg A 1331) (e.g., the transport block 1342).

A wireless device and a base station may exchange control signaling(e.g., control information). The control signaling may be referred to asL1/L2 control signaling and may originate from the PHY layer (e.g.,layer 1) and/or the MAC layer (e.g., layer 2) of the wireless device orthe base station. The control signaling may comprise downlink controlsignaling sent/transmitted from the base station to the wireless deviceand/or uplink control signaling sent/transmitted from the wirelessdevice to the base station.

The downlink control signaling may comprise at least one of: a downlinkscheduling assignment; an uplink scheduling grant indicating uplinkradio resources and/or a transport format; slot format information; apreemption indication; a power control command; and/or any othersuitable signaling. The wireless device may receive the downlink controlsignaling in a payload sent/transmitted by the base station via a PDCCH.The payload sent/transmitted via the PDCCH may be referred to asdownlink control information (DCI). The PDCCH may be a group commonPDCCH (GC-PDCCH) that is common to a group of wireless devices. TheGC-PDCCH may be scrambled by a group common RNTI.

A base station may attach one or more cyclic redundancy check (CRC)parity bits to DCI, for example, in order to facilitate detection oftransmission errors. The base station may scramble the CRC parity bitswith an identifier of a wireless device (or an identifier of a group ofwireless devices), for example, if the DCI is intended for the wirelessdevice (or the group of the wireless devices). Scrambling the CRC paritybits with the identifier may comprise Modulo-2 addition (or anexclusive-OR operation) of the identifier value and the CRC parity bits.The identifier may comprise a 16-bit value of an RNTI.

DCIs may be used for different purposes. A purpose may be indicated bythe type of an RNTI used to scramble the CRC parity bits. DCI having CRCparity bits scrambled with a paging RNTI (P-RNTI) may indicate paginginformation and/or a system information change notification. The P-RNTImay be predefined as “FFFE” in hexadecimal. DCI having CRC parity bitsscrambled with a system information RNTI (SI-RNTI) may indicate abroadcast transmission of the system information. The SI-RNTI may bepredefined as “FFFF” in hexadecimal. DCI having CRC parity bitsscrambled with a random access RNTI (RA-RNTI) may indicate a randomaccess response (RAR). DCI having CRC parity bits scrambled with a cellRNTI (C-RNTI) may indicate a dynamically scheduled unicast transmissionand/or a triggering of PDCCH-ordered random access. DCI having CRCparity bits scrambled with a temporary cell RNTI (TC-RNTI) may indicatea contention resolution (e.g., a Msg 3 analogous to the Msg 3 1313 shownin FIG. 13A). Other RNTIs configured for a wireless device by a basestation may comprise a Configured Scheduling RNTI (CS RNTI), a TransmitPower Control-PUCCH RNTI (TPC PUCCH-RNTI), a Transmit PowerControl-PUSCH RNTI (TPC-PUSCH-RNTI), a Transmit Power Control-SRS RNTI(TPC-SRS-RNTI), an Interruption RNTI (INT-RNTI), a Slot FormatIndication RNTI (SFI-RNTI), a Semi-Persistent CSI RNTI (SP-CSI-RNTI), aModulation and Coding Scheme Cell RNTI (MCS-C RNTI), and/or the like.

A base station may send/transmit DCIs with one or more DCI formats, forexample, depending on the purpose and/or content of the DCIs. DCI format0_0 may be used for scheduling of a PUSCH in a cell. DCI format 0_0 maybe a fallback DCI format (e.g., with compact DCI payloads). DCI format0_1 may be used for scheduling of a PUSCH in a cell (e.g., with more DCIpayloads than DCI format 0_0). DCI format 1_0 may be used for schedulingof a PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g.,with compact DCI payloads). DCI format 1_1 may be used for scheduling ofa PDSCH in a cell (e.g., with more DCI payloads than DCI format 1_0).DCI format 2_0 may be used for providing a slot format indication to agroup of wireless devices. DCI format 2_1 may be used forinforming/notifying a group of wireless devices of a physical resourceblock and/or an OFDM symbol where the group of wireless devices mayassume no transmission is intended to the group of wireless devices. DCIformat 2_2 may be used for transmission of a transmit power control(TPC) command for PUCCH or PUSCH. DCI format 2_3 may be used fortransmission of a group of TPC commands for SRS transmissions by one ormore wireless devices. DCI format(s) for new functions may be defined infuture releases. DCI formats may have different DCI sizes, or may sharethe same DCI size.

The base station may process the DCI with channel coding (e.g., polarcoding), rate matching, scrambling and/or QPSK modulation, for example,after scrambling the DCI with an RNTI. A base station may map the codedand modulated DCI on resource elements used and/or configured for aPDCCH. The base station may send/transmit the DCI via a PDCCH occupyinga number of contiguous control channel elements (CCEs), for example,based on a payload size of the DCI and/or a coverage of the basestation. The number of the contiguous CCEs (referred to as aggregationlevel) may be 1, 2, 4, 8, 16, and/or any other suitable number. A CCEmay comprise a number (e.g., 6) of resource-element groups (REGs). A REGmay comprise a resource block in an OFDM symbol. The mapping of thecoded and modulated DCI on the resource elements may be based on mappingof CCEs and REGs (e.g., CCE-to-REG mapping).

FIG. 14A shows an example of CORESET configurations. The CORESETconfigurations may be for a bandwidth part or any other frequency bands.The base station may send/transmit DCI via a PDCCH on one or morecontrol resource sets (CORESETs). A CORESET may comprise atime-frequency resource in which the wireless device attempts/tries todecode DCI using one or more search spaces. The base station mayconfigure a size and a location of the CORESET in the time-frequencydomain. A first CORESET 1401 and a second CORESET 1402 may occur or maybe set/configured at the first symbol in a slot. The first CORESET 1401may overlap with the second CORESET 1402 in the frequency domain. Athird CORESET 1403 may occur or may be set/configured at a third symbolin the slot. A fourth CORESET 1404 may occur or may be set/configured atthe seventh symbol in the slot. CORESETs may have a different number ofresource blocks in frequency domain.

FIG. 14B shows an example of a CCE-to-REG mapping. The CCE-to-REGmapping may be performed for DCI transmission via a CORESET and PDCCHprocessing. The CCE-to-REG mapping may be an interleaved mapping (e.g.,for the purpose of providing frequency diversity) or a non-interleavedmapping (e.g., for the purposes of facilitating interferencecoordination and/or frequency-selective transmission of controlchannels). The base station may perform different or same CCE-to-REGmapping on different CORESETs. A CORESET may be associated with aCCE-to-REG mapping (e.g., by an RRC configuration). A CORESET may beconfigured with an antenna port QCL parameter. The antenna port QCLparameter may indicate QCL information of a DM-RS for a PDCCH receptionvia the CORESET.

The base station may send/transmit, to the wireless device, one or moreRRC messages comprising configuration parameters of one or more CORESETsand one or more search space sets. The configuration parameters mayindicate an association between a search space set and a CORESET. Asearch space set may comprise a set of PDCCH candidates formed by CCEs(e.g., at a given aggregation level). The configuration parameters mayindicate at least one of: a number of PDCCH candidates to be monitoredper aggregation level; a PDCCH monitoring periodicity and a PDCCHmonitoring pattern; one or more DCI formats to be monitored by thewireless device; and/or whether a search space set is a common searchspace set or a wireless device-specific search space set (e.g., aUE-specific search space set). A set of CCEs in the common search spaceset may be predefined and known to the wireless device. A set of CCEs inthe wireless device-specific search space set (e.g., the UE-specificsearch space set) may be configured, for example, based on the identityof the wireless device (e.g., C-RNTI).

As shown in FIG. 14B, the wireless device may determine a time-frequencyresource for a CORESET based on one or more RRC messages. The wirelessdevice may determine a CCE-to-REG mapping (e.g., interleaved ornon-interleaved, and/or mapping parameters) for the CORESET, forexample, based on configuration parameters of the CORESET. The wirelessdevice may determine a number (e.g., at most 10) of search space setsconfigured on/for the CORESET, for example, based on the one or more RRCmessages. The wireless device may monitor a set of PDCCH candidatesaccording to configuration parameters of a search space set. Thewireless device may monitor a set of PDCCH candidates in one or moreCORESETs for detecting one or more DCIs. Monitoring may comprisedecoding one or more PDCCH candidates of the set of the PDCCH candidatesaccording to the monitored DCI formats. Monitoring may comprise decodingDCI content of one or more PDCCH candidates with possible (orconfigured) PDCCH locations, possible (or configured) PDCCH formats(e.g., the number of CCEs, the number of PDCCH candidates in commonsearch spaces, and/or the number of PDCCH candidates in the wirelessdevice-specific search spaces) and possible (or configured) DCI formats.The decoding may be referred to as blind decoding. The wireless devicemay determine DCI as valid for the wireless device, for example, afteror in response to CRC checking (e.g., scrambled bits for CRC parity bitsof the DCI matching an RNTI value). The wireless device may processinformation comprised in the DCI (e.g., a scheduling assignment, anuplink grant, power control, a slot format indication, a downlinkpreemption, and/or the like).

The may send/transmit uplink control signaling (e.g., UCI) to a basestation. The uplink control signaling may comprise HARQ acknowledgementsfor received DL-SCH transport blocks. The wireless device maysend/transmit the HARQ acknowledgements, for example, after or inresponse to receiving a DL-SCH transport block. Uplink control signalingmay comprise CSI indicating a channel quality of a physical downlinkchannel. The wireless device may send/transmit the CSI to the basestation. The base station, based on the received CSI, may determinetransmission format parameters (e.g., comprising multi-antenna andbeamforming schemes) for downlink transmission(s). Uplink controlsignaling may comprise scheduling requests (SR). The wireless device maysend/transmit an SR indicating that uplink data is available fortransmission to the base station. The wireless device may send/transmitUCI (e.g., HARQ acknowledgements (HARQ-ACK), CSI report, SR, and thelike) via a PUCCH or a PUSCH. The wireless device may send/transmit theuplink control signaling via a PUCCH using one of several PUCCH formats.

There may be multiple PUCCH formats (e.g., five PUCCH formats). Awireless device may determine a PUCCH format, for example, based on asize of UCI (e.g., a quantity/number of uplink symbols of UCItransmission and a number of UCI bits). PUCCH format 0 may have a lengthof one or two OFDM symbols and may comprise two or fewer bits. Thewireless device may send/transmit UCI via a PUCCH resource, for example,using PUCCH format 0 if the transmission is over/via one or two symbolsand the quantity/number of HARQ-ACK information bits with positive ornegative SR (HARQ-ACK/SR bits) is one or two. PUCCH format 1 may occupya number of OFDM symbols (e.g., between four and fourteen OFDM symbols)and may comprise two or fewer bits. The wireless device may use PUCCHformat 1, for example, if the transmission is over/via four or moresymbols and the number of HARQ-ACK/SR bits is one or two. PUCCH format 2may occupy one or two OFDM symbols and may comprise more than two bits.The wireless device may use PUCCH format 2, for example, if thetransmission is over/via one or two symbols and the quantity/number ofUCI bits is two or more. PUCCH format 3 may occupy a number of OFDMsymbols (e.g., between four and fourteen OFDM symbols) and may comprisemore than two bits. The wireless device may use PUCCH format 3, forexample, if the transmission is four or more symbols, thequantity/number of UCI bits is two or more, and the PUCCH resource doesnot comprise an orthogonal cover code (OCC). PUCCH format 4 may occupy anumber of OFDM symbols (e.g., between four and fourteen OFDM symbols)and may comprise more than two bits. The wireless device may use PUCCHformat 4, for example, if the transmission is four or more symbols, thequantity/number of UCI bits is two or more, and the PUCCH resourcecomprises an OCC.

The base station may send/transmit configuration parameters to thewireless device for a plurality of PUCCH resource sets, for example,using an RRC message. The plurality of PUCCH resource sets (e.g., up tofour sets in NR, or up to any other quantity of sets in other systems)may be configured on an uplink BWP of a cell. A PUCCH resource set maybe configured with a PUCCH resource set index, a plurality of PUCCHresources with a PUCCH resource being identified by a PUCCH resourceidentifier (e.g., pucch-Resourceid), and/or a number (e.g. a maximumnumber) of UCI information bits the wireless device may send/transmitusing one of the plurality of PUCCH resources in the PUCCH resource set.The wireless device may select one of the plurality of PUCCH resourcesets, for example, based on a total bit length of the UCI informationbits (e.g., HARQ-ACK, SR, and/or CSI) if configured with a plurality ofPUCCH resource sets. The wireless device may select a first PUCCHresource set having a PUCCH resource set index equal to “0,” forexample, if the total bit length of UCI information bits is two orfewer. The wireless device may select a second PUCCH resource set havinga PUCCH resource set index equal to “1,” for example, if the total bitlength of UCI information bits is greater than two and less than orequal to a first configured value. The wireless device may select athird PUCCH resource set having a PUCCH resource set index equal to “2,”for example, if the total bit length of UCI information bits is greaterthan the first configured value and less than or equal to a secondconfigured value. The wireless device may select a fourth PUCCH resourceset having a PUCCH resource set index equal to “3,” for example, if thetotal bit length of UCI information bits is greater than the secondconfigured value and less than or equal to a third value (e.g., 1406,1706, or any other quantity of bits).

The wireless device may determine a PUCCH resource from the PUCCHresource set for UCI (HARQ-ACK, CSI, and/or SR) transmission, forexample, after determining a PUCCH resource set from a plurality ofPUCCH resource sets. The wireless device may determine the PUCCHresource, for example, based on a PUCCH resource indicator in DCI (e.g.,with DCI format 1_0 or DCI for 1_1) received on/via a PDCCH. An n-bit(e.g., a three-bit) PUCCH resource indicator in the DCI may indicate oneof multiple (e.g., eight) PUCCH resources in the PUCCH resource set. Thewireless device may send/transmit the UCI (HARQ-ACK, CSI and/or SR)using a PUCCH resource indicated by the PUCCH resource indicator in theDCI, for example, based on the PUCCH resource indicator.

FIG. 15A shows an example communications between a wireless device and abase station. A wireless device 1502 and a base station 1504 may be partof a communication network, such as the communication network 100 shownin FIG. 1A, the communication network 150 shown in FIG. 1B, or any othercommunication network. A communication network may comprise more thanone wireless device and/or more than one base station, withsubstantially the same or similar configurations as those shown in FIG.15A.

The base station 1504 may connect the wireless device 1502 to a corenetwork (not shown) via radio communications over the air interface (orradio interface) 1506. The communication direction from the base station1504 to the wireless device 1502 over the air interface 1506 may bereferred to as the downlink. The communication direction from thewireless device 1502 to the base station 1504 over the air interface maybe referred to as the uplink. Downlink transmissions may be separatedfrom uplink transmissions, for example, using various duplex schemes(e.g., FDD, TDD, and/or some combination of the duplexing techniques).

For the downlink, data to be sent to the wireless device 1502 from thebase station 1504 may be provided/transferred/sent to the processingsystem 1508 of the base station 1504. The data may beprovided/transferred/sent to the processing system 1508 by, for example,a core network. For the uplink, data to be sent to the base station 1504from the wireless device 1502 may be provided/transferred/sent to theprocessing system 1518 of the wireless device 1502. The processingsystem 1508 and the processing system 1518 may implement layer 3 andlayer 2 OSI functionality to process the data for transmission. Layer 2may comprise an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer,for example, described with respect to FIG. 2A, FIG. 2B, FIG. 3, andFIG. 4A. Layer 3 may comprise an RRC layer, for example, described withrespect to FIG. 2B.

The data to be sent to the wireless device 1502 may beprovided/transferred/sent to a transmission processing system 1510 ofbase station 1504, for example, after being processed by the processingsystem 1508. The data to be sent to base station 1504 may beprovided/transferred/sent to a transmission processing system 1520 ofthe wireless device 1502, for example, after being processed by theprocessing system 1518. The transmission processing system 1510 and thetransmission processing system 1520 may implement layer 1 OSIfunctionality. Layer 1 may comprise a PHY layer, for example, describedwith respect to FIG. 2A, FIG. 2B, FIG. 3, and FIG. 4A. For transmitprocessing, the PHY layer may perform, for example, forward errorcorrection coding of transport channels, interleaving, rate matching,mapping of transport channels to physical channels, modulation ofphysical channel, multiple-input multiple-output (MIMO) or multi-antennaprocessing, and/or the like.

A reception processing system 1512 of the base station 1504 may receivethe uplink transmission from the wireless device 1502. The receptionprocessing system 1512 of the base station 1504 may comprise one or moreTRPs. A reception processing system 1522 of the wireless device 1502 mayreceive the downlink transmission from the base station 1504. Thereception processing system 1522 of the wireless device 1502 maycomprise one or more antenna panels. The reception processing system1512 and the reception processing system 1522 may implement layer 1 OSIfunctionality. Layer 1 may include a PHY layer, for example, describedwith respect to FIG. 2A, FIG. 2B, FIG. 3, and FIG. 4A. For receiveprocessing, the PHY layer may perform, for example, error detection,forward error correction decoding, deinterleaving, demapping oftransport channels to physical channels, demodulation of physicalchannels, MIMO or multi-antenna processing, and/or the like.

The base station 1504 may comprise multiple antennas (e.g., multipleantenna panels, multiple

TRPs, etc.). The wireless device 1502 may comprise multiple antennas(e.g., multiple antenna panels, etc.). The multiple antennas may be usedto perform one or more MIMO or multi-antenna techniques, such as spatialmultiplexing (e.g., single-user MIMO or multi-user MIMO),transmit/receive diversity, and/or beamforming. The wireless device 1502and/or the base station 1504 may have a single antenna.

The processing system 1508 and the processing system 1518 may beassociated with a memory 1514 and a memory 1524, respectively. Memory1514 and memory 1524 (e.g., one or more non-transitory computer readablemediums) may store computer program instructions or code that may beexecuted by the processing system 1508 and/or the processing system1518, respectively, to carry out one or more of the functionalities(e.g., one or more functionalities described herein and otherfunctionalities of general computers, processors, memories, and/or otherperipherals). The transmission processing system 1510 and/or thereception processing system 1512 may be coupled to the memory 1514and/or another memory (e.g., one or more non-transitory computerreadable mediums) storing computer program instructions or code that maybe executed to carry out one or more of their respectivefunctionalities. The transmission processing system 1520 and/or thereception processing system 1522 may be coupled to the memory 1524and/or another memory (e.g., one or more non-transitory computerreadable mediums) storing computer program instructions or code that maybe executed to carry out one or more of their respectivefunctionalities.

The processing system 1508 and/or the processing system 1518 maycomprise one or more controllers and/or one or more processors. The oneor more controllers and/or one or more processors may comprise, forexample, a general-purpose processor, a digital signal processor (DSP),a microcontroller, an application specific integrated circuit (ASIC), afield programmable gate array (FPGA) and/or other programmable logicdevice, discrete gate and/or transistor logic, discrete hardwarecomponents, an on-board unit, or any combination thereof. The processingsystem 1508 and/or the processing system 1518 may perform at least oneof signal coding/processing, data processing, power control,input/output processing, and/or any other functionality that may enablethe wireless device 1502 and/or the base station 1504 to operate in awireless environment.

The processing system 1508 may be connected to one or more peripherals1516. The processing system 1518 may be connected to one or moreperipherals 1526. The one or more peripherals 1516 and the one or moreperipherals 1526 may comprise software and/or hardware that providefeatures and/or functionalities, for example, a speaker, a microphone, akeypad, a display, a touchpad, a power source, a satellite transceiver,a universal serial bus (USB) port, a hands-free headset, a frequencymodulated (FM) radio unit, a media player, an Internet browser, anelectronic control unit (e.g., for a motor vehicle), and/or one or moresensors (e.g., an accelerometer, a gyroscope, a temperature sensor, aradar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, acamera, and/or the like). The processing system 1508 and/or theprocessing system 1518 may receive input data (e.g., user input data)from, and/or provide output data (e.g., user output data) to, the one ormore peripherals 1516 and/or the one or more peripherals 1526. Theprocessing system 1518 in the wireless device 1502 may receive powerfrom a power source and/or may be configured to distribute the power tothe other components in the wireless device 1502. The power source maycomprise one or more sources of power, for example, a battery, a solarcell, a fuel cell, or any combination thereof. The processing system1508 may be connected to a Global Positioning System (GPS) chipset 1517.The processing system 1518 may be connected to a Global PositioningSystem (GPS) chipset 1527. The GPS chipset 1517 and the GPS chipset 1527may be configured to determine and provide geographic locationinformation of the wireless device 1502 and the base station 1504,respectively.

FIG. 15B shows example elements of a computing device that may be usedto implement any of the various devices described herein, including, forexample, the base station 160A, 160B, 162A, 162B, 220, and/or 1504, thewireless device 106, 156A, 156B, 210, and/or 1502, or any other basestation, wireless device, AMF, UPF, network device, or computing devicedescribed herein. The computing device 1530 may include one or moreprocessors 1531, which may execute instructions stored in therandom-access memory (RAM) 1533, the removable media 1534 (such as aUniversal Serial Bus (USB) drive, compact disk (CD) or digital versatiledisk (DVD), or floppy disk drive), or any other desired storage medium.Instructions may also be stored in an attached (or internal) hard drive1535. The computing device 1530 may also include a security processor(not shown), which may execute instructions of one or more computerprograms to monitor the processes executing on the processor 1531 andany process that requests access to any hardware and/or softwarecomponents of the computing device 1530 (e.g., ROM 1532, RAM 1533, theremovable media 1534, the hard drive 1535, the device controller 1537, anetwork interface 1539, a GPS 1541, a Bluetooth interface 1542, a WiFiinterface 1543, etc.). The computing device 1530 may include one or moreoutput devices, such as the display 1536 (e.g., a screen, a displaydevice, a monitor, a television, etc.), and may include one or moreoutput device controllers 1537, such as a video processor. There mayalso be one or more user input devices 1538, such as a remote control,keyboard, mouse, touch screen, microphone, etc. The computing device1530 may also include one or more network interfaces, such as a networkinterface 1539, which may be a wired interface, a wireless interface, ora combination of the two. The network interface 1539 may provide aninterface for the computing device 1530 to communicate with a network1540 (e.g., a RAN, or any other network). The network interface 1539 mayinclude a modem (e.g., a cable modem), and the external network 1540 mayinclude communication links, an external network, an in-home network, aprovider's wireless, coaxial, fiber, or hybrid fiber/coaxialdistribution system (e.g., a DOCSIS network), or any other desirednetwork. Additionally, the computing device 1530 may include alocation-detecting device, such as a global positioning system (GPS)microprocessor 1541, which may be configured to receive and processglobal positioning signals and determine, with possible assistance froman external server and antenna, a geographic position of the computingdevice 1530.

The example in FIG. 15B may be a hardware configuration, although thecomponents shown may be implemented as software as well. Modificationsmay be made to add, remove, combine, divide, etc. components of thecomputing device 1530 as desired. Additionally, the components may beimplemented using basic computing devices and components, and the samecomponents (e.g., processor 1531, ROM storage 1532, display 1536, etc.)may be used to implement any of the other computing devices andcomponents described herein. For example, the various componentsdescribed herein may be implemented using computing devices havingcomponents such as a processor executing computer-executableinstructions stored on a computer-readable medium, as shown in FIG. 15B.Some or all of the entities described herein may be software based, andmay co-exist in a common physical platform (e.g., a requesting entitymay be a separate software process and program from a dependent entity,both of which may be executed as software on a common computing device).

FIG. 16A shows an example structure for uplink transmission. Processingof a baseband signal representing a physical uplink shared channel maycomprise/perform one or more functions. The one or more functions maycomprise at least one of: scrambling; modulation of scrambled bits togenerate complex-valued symbols; mapping of the complex-valuedmodulation symbols onto one or several transmission layers; transformprecoding to generate complex-valued symbols; precoding of thecomplex-valued symbols; mapping of precoded complex-valued symbols toresource elements; generation of complex-valued time-domain SingleCarrier-Frequency Division Multiple Access (SC-FDMA), CP-OFDM signal foran antenna port, or any other signals; and/or the like. An SC-FDMAsignal for uplink transmission may be generated, for example, iftransform precoding is enabled. A CP-OFDM signal for uplink transmissionmay be generated, for example, if transform precoding is not enabled(e.g., as shown in FIG. 16A). These functions are examples and othermechanisms for uplink transmission may be implemented.

FIG. 16B shows an example structure for modulation and up-conversion ofa baseband signal to a carrier frequency. The baseband signal may be acomplex-valued SC-FDMA, CP-OFDM baseband signal (or any other basebandsignals) for an antenna port and/or a complex-valued Physical RandomAccess Channel (PRACH) baseband signal. Filtering may beperformed/employed, for example, prior to transmission.

FIG. 16C shows an example structure for downlink transmissions.Processing of a baseband signal representing a physical downlink channelmay comprise/perform one or more functions. The one or more functionsmay comprise: scrambling of coded bits in a codeword to besent/transmitted on/via a physical channel; modulation of scrambled bitsto generate complex-valued modulation symbols; mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers; precoding of the complex-valued modulation symbols on a layerfor transmission on the antenna ports; mapping of complex-valuedmodulation symbols for an antenna port to resource elements; generationof complex-valued time-domain OFDM signal for an antenna port; and/orthe like. These functions are examples and other mechanisms for downlinktransmission may be implemented.

FIG. 16D shows an example structure for modulation and up-conversion ofa baseband signal to a carrier frequency. The baseband signal may be acomplex-valued OFDM baseband signal for an antenna port or any othersignal. Filtering may be performed/employed, for example, prior totransmission.

A wireless device may receive, from a base station, one or more messages(e.g. RRC messages) comprising configuration parameters of a pluralityof cells (e.g., a primary cell, one or more secondary cells). Thewireless device may communicate with at least one base station (e.g.,two or more base stations in dual-connectivity) via the plurality ofcells. The one or more messages (e.g. as a part of the configurationparameters) may comprise parameters of PHY, MAC, RLC, PCDP, SDAP, RRClayers for configuring the wireless device. The configuration parametersmay comprise parameters for configuring PHY and MAC layer channels,bearers, etc. The configuration parameters may comprise parametersindicating values of timers for PHY, MAC, RLC, PCDP, SDAP, RRC layers,and/or communication channels.

A timer may begin running, for example, once it is started and continuerunning until it is stopped or until it expires. A timer may be started,for example, if it is not running or restarted if it is running A timermay be associated with a value (e.g., the timer may be started orrestarted from a value or may be started from zero and expire once itreaches the value). The duration of a timer may not be updated, forexample, until the timer is stopped or expires (e.g., due to BWPswitching). A timer may be used to measure a time period/window for aprocess. With respect to an implementation and/or procedure related toone or more timers or other parameters, it will be understood that theremay be multiple ways to implement the one or more timers or otherparameters. One or more of the multiple ways to implement a timer may beused to measure a time period/window for the procedure. A random accessresponse window timer may be used for measuring a window of time forreceiving a random access response. The time difference between two timestamps may be used, for example, instead of starting a random accessresponse window timer and determine the expiration of the timer. Aprocess for measuring a time window may be restarted, for example, if atimer is restarted. Other example implementations may beconfigured/provided to restart a measurement of a time window.

A base station may communicate with a wireless device via a wirelessnetwork (e.g., a communication network). The communications mayuse/employ one or more radio technologies (e.g., new radio technologies,legacy radio technologies, and/or a combination thereof). The one ormore radio technologies may comprise at least one of: one or multipletechnologies related to a physical layer; one or multiple technologiesrelated to a medium access control layer; and/or one or multipletechnologies related to a radio resource control layer. One or moreenhanced radio technologies described herein may improve performance ofa wireless network. System throughput, transmission efficiencies of awireless network, and/or data rate of transmission may be improved, forexample, based on one or more configurations described herein. Batteryconsumption of a wireless device may be reduced, for example, based onone or more configurations described herein. Latency of datatransmission between a base station and a wireless device may beimproved, for example, based on one or more configurations describedherein. A network coverage of a wireless network may increase, forexample, based on one or more configurations described herein.

A base station may send/transmit one or more MAC PDUs to a wirelessdevice. A MAC PDU may be a bit string that is byte aligned (e.g., amultiple of eight bits) in length. Bit strings may be represented by oneor more tables in which the most significant bit may be the leftmost bitof the first line of a table, and the least significant bit may be therightmost bit on the last line of the table. The bit string may be readfrom left to right and then in the reading order of the lines (e.g.,from the topmost line of the table to the bottommost line of the table).The bit order of a parameter field within a MAC PDU may be representedwith the first and most significant bit in the leftmost bit and the lastand least significant bit in the rightmost bit.

A MAC SDU may be a bit string that is byte aligned (e.g., a multiple ofeight bits) in length. A MAC SDU may be comprised in a MAC PDU from thefirst bit onward. A MAC CE may be a bit string that is byte aligned(e.g., a multiple of eight bits) in length. A MAC subheader may be a bitstring that is byte aligned (e.g., a multiple of eight bits) in length.A MAC subheader may be placed immediately in front of a correspondingMAC SDU, MAC CE, or padding. A wireless device (e.g., the MAC entity ofthe wireless device) may ignore a value of reserved bits in a downlink(DL) MAC PDU.

A MAC PDU may comprise one or more MAC subPDUs. A MAC subPDU of the oneor more MAC subPDUs may comprise: a MAC subheader only (includingpadding); a MAC subheader and a MAC SDU; a MAC subheader and a MAC CE;and/or a MAC subheader and padding. The MAC SDU may be of variable size.A MAC subheader may correspond to a MAC SDU, a MAC CE, or padding.

A MAC subheader may comprise: an R field with a one-bit length; an Ffield with a one-bit length; an LCID field with a multi-bit length;and/or an L field with a multi-bit length, for example, if the MACsubheader corresponds to a MAC SDU, a variable-sized MAC CE, or padding.

FIG. 17A shows an example of a MAC subheader. The MAC subheader maycomprise an R field, an F field, an LCID field, and/or an L field. TheLCID field may be six bits in length (or any other quantity of bits).The L field may be eight bits in length (or any other quantity of bits).Each of the R field and the F field may be one bit in length (or anyother quantity of bits). FIG. 17B shows an example of a MAC subheader.The MAC subheader may comprise an R field, an F field, an LCID field,and/or an L field. Similar to the MAC subheader shown in FIG. 17A, theLCID field may be six bits in length (or any other quantity of bits),the R field may be one bit in length (or any other quantity of bits),and the F field may be one bit in length (or any other quantity ofbits). The L field may be sixteen bits in length (or any other quantityof bits, such as greater than sixteen bits in length). A MAC subheadermay comprise: an R field with a two-bit length (or any other quantity ofbits) and/or an LCID field with a multi-bit length (or single bitlength), for example, if the MAC subheader corresponds to a fixed sizedMAC CE or padding. FIG. 17C shows an example of a MAC subheader. In theexample MAC subheader shown in FIG. 17C, the LCID field may be six bitsin length (or any other quantity of bits), and the R field may be twobits in length (or any other quantity of bits).

FIG. 18A shows an example of a MAC PDU (e.g., a DL MAC PDU). MultipleMAC CEs, such as MAC CE 1 and 2 shown in FIG. 18A, may be placedtogether (e.g., located within the same MAC PDU). A MAC subPDUcomprising a MAC CE may be placed (e.g., located within a MAC PDU)before any MAC subPDU comprising a MAC SDU or a MAC subPDU comprisingpadding. MAC CE 1 may be a fixed-sized MAC CE that follows a first-typeMAC subheader. The first-type MAC subheader may comprise an R field andan LCID field (e.g., similar to the MAC CE shown in FIG. 17C). MAC CE 2may be a variable-sized MAC CE that follows a second-type MAC subheader.The second-type MAC subheader may comprise an R field, an F field, anLCID field and an L field (e.g., similar to the MAC CEs shown in FIG.17A or FIG. 17B). The size of a MAC SDU that follows the second-type MACsubheader may vary.

FIG. 18B shows an example of a MAC PDU (e.g., a UL MAC PDU). MultipleMAC CEs, such as MAC CE 1 and 2 shown in FIG. 18B, may be placedtogether (e.g., located within the same MAC PDU). A MAC subPDUcomprising a MAC CE may be placed (e.g., located within a MAC PDU) afterall MAC subPDUs comprising a MAC SDU. The MAC subPDU and/or the MACsubPDU comprising a MAC CE may be placed (e.g., located within a MACPDU) before a MAC subPDU comprising padding. Similar to the MAC CEsshown in FIG. 18A, MAC CE 1 shown in FIG. 18B may be a fixed-sized MACCE that follows a first-type MAC subheader. The first-type MAC subheadermay comprise an R field and an LCID field (e.g., similar to the MAC CEshown in FIG. 17C). Similar to the MAC CEs shown in FIG. 18A, MAC CE 2shown in FIG. 18B may be a variable-sized MAC CE that follows asecond-type MAC subheader. The second-type MAC subheader may comprise anR field, an F field, an LCID field and an L field (e.g., similar to theMAC CEs shown in FIG. 17A or FIG. 17B). The size of a MAC SDU thatfollows the second-type MAC subheader may vary.

A base station (e.g., the MAC entity of a base station) maysend/transmit one or more MAC CEs to a wireless device (e.g., a MACentity of a wireless device). FIG. 19 shows example LCID values. TheLCID values may be associated with one or more MAC CEs. The LCID valuesmay be associated with a downlink channel, such as a DL-SCH. The one ormore MAC CEs may comprise at least one of: an semi-persistent zero powerCSI-RS (SP ZP CSI-RS) Resource Set Activation/Deactivation MAC CE, aPUCCH spatial relation Activation/Deactivation MAC CE, an SP SRSActivation/Deactivation MAC CE, an SP CSI reporting on PUCCHActivation/Deactivation MAC CE, a TCI State Indication for wirelessdevice-specific (e.g., UE-specific) PDCCH MAC CE, a TCI State Indicationfor wireless device-specific (e.g., UE-specific) PDSCH MAC CE, anAperiodic CSI Trigger State Subselection MAC CE, an SP CSI-RS/CSIinterference measurement (CSI-IM) Resource Set Activation/DeactivationMAC CE, a wireless device (e.g., UE) contention resolution identity MACCE, a timing advance command MAC CE, a DRX command MAC CE, a Long DRXcommand MAC CE, an SCell activation/deactivation MAC CE (e.g., 1 Octet),an SCell activation/deactivation MAC CE (e.g., 4 Octet), and/or aduplication activation/deactivation MAC CE. A MAC CE, such as a MAC CEsent/transmitted by a base station (e.g., a MAC entity of a basestation) to a wireless device (e.g., a MAC entity of a wireless device),may be associated with (e.g., correspond to) an LCID in the MACsubheader corresponding to the MAC CE. Different MAC CEs may correspondto a different LCID in the MAC subheader corresponding to thecorresponding MAC CE. An LCID having an index value “111011” in a MACsubheader may indicate that a MAC CE associated with the MAC subheaderis a long DRX command MAC CE, for example, for a MAC CE associated withthe downlink.

A wireless device (e.g., a MAC entity of a wireless device) maysend/transmit to a base station (e.g., a MAC entity of a base station)one or more MAC CEs. FIG. 20 shows an example LCID values that may beassociated with the one or more MAC CEs. The LCID values may beassociated with an uplink channel, such as a UL-SCH. The one or more MACCEs may comprise at least one of: a short buffer status report (BSR) MACCE, a long BSR MAC CE, a C-RNTI MAC CE, a configured grant confirmationMAC CE, a single entry power headroom report (PHR) MAC CE, a multipleentry PHR MAC CE, a short truncated BSR, and/or a long truncated BSR. AMAC CE may be associated with (e.g., correspond to) an LCID in the MACsubheader corresponding to the MAC CE. Different MAC CEs may correspondto a different LCID in the MAC subheader corresponding to the MAC CE. AnLCID having an index value “111011” in a MAC subheader may indicate thata MAC CE associated with the MAC subheader is a short-truncated commandMAC CE, for example, for a MAC CE associated with the uplink.

Two or more component carriers (CCs) may be aggregated, such as incarrier aggregation (CA). A wireless device may simultaneously receiveand/or transmit data via one or more CCs, for example, depending oncapabilities of the wireless device (e.g., using the technique of CA). Awireless device may support CA for contiguous CCs and/or fornon-contiguous CCs. CCs may be organized into cells. CCs may beorganized into one PCell and one or more SCells.

A wireless device may have an RRC connection (e.g., one RRC connection)with a network, for example, if the wireless device is configured withCA. During an RRC connection establishment/re-establishment/handover, acell providing/sending/configuring NAS mobility information may be aserving cell. During an RRC connection re-establishment/handoverprocedure, a cell providing/sending/configuring a security input may bea serving cell. The serving cell may be a PCell. A base station maysend/transmit, to a wireless device, one or more messages comprisingconfiguration parameters of a plurality of SCells, for example,depending on capabilities of the wireless device.

A base station and/or a wireless device may use/employ anactivation/deactivation mechanism of an SCell, for example, ifconfigured with CA. The base station and/or the wireless device mayuse/employ an activation/deactivation mechanism of an SCell, forexample, to improve battery use and/or power consumption of the wirelessdevice. A base station may activate or deactivate at least one of one ormore SCells, for example, if a wireless device is configured with theone or more SCells. An SCell may be deactivated unless an SCell stateassociated with the SCell is set to an activated state (e.g.,“activated”) or a dormant state (e.g., “dormant”), for example, afterconfiguring the SCell.

A wireless device may activate/deactivate an SCell. A wireless devicemay activate/deactivate a cell, for example, based on (e.g., after or inresponse to) receiving an SCell Activation/Deactivation MAC CE. TheSCell Activation/Deactivation MAC CE may comprise one or more fieldsassociated with one or more SCells, respectively, to indicate activationor deactivation of the one or more SCells. The SCellActivation/Deactivation MAC CE may correspond to one octet comprisingseven fields associated with up to seven SCells, respectively, forexample, if the aggregated cell has less than eight SCells. The SCellActivation/Deactivation MAC CE may comprise an R field. The SCellActivation/Deactivation MAC CE may comprise a plurality of octetscomprising more than seven fields associated with more than sevenSCells, for example, if the aggregated cell has more than seven SCells.

FIG. 21A shows an example SCell Activation/Deactivation MAC CE of oneoctet. A first MAC PDU subheader comprising a first LCID (e.g., ‘111010’as shown in FIG. 19) may indicate/identify the SCellActivation/Deactivation MAC CE of one octet. The SCellActivation/Deactivation MAC CE of one octet may have a fixed size. TheSCell Activation/Deactivation MAC CE of one octet may comprise a singleoctet. The single octet may comprise a first quantity/number of C-fields(e.g., seven or any other quantity/number) and a second quantity/numberof R-fields (e.g., one or any other quantity/number).

FIG. 21B shows an example SCell Activation/Deactivation MAC CE of fouroctets. A second MAC PDU subheader comprising a second LCID (e.g.,‘111001’ as shown in FIG. 19) may indicate/identify the SCellActivation/Deactivation MAC CE of four octets. The SCellActivation/Deactivation MAC CE of four octets may have a fixed size. TheSCell Activation/Deactivation MAC CE of four octets may comprise fouroctets. The four octets may comprise a third quantity/number of C-fields(e.g., 31 or any other quantity/number) and a fourth quantity/number ofR-fields (e.g., 1 or any other quantity/number).

As shown in FIG. 21A and/or FIG. 21B, a Ci field may indicate anactivation/deactivation status of an SCell with/corresponding to anSCell index i, for example, if an SCell with/corresponding to SCellindex i is configured. An SCell with an SCell index i may be activated,for example, if the Ci field is set to one. An SCell with an SCell indexi may be deactivated, for example, if the Ci field is set to zero. Thewireless device may ignore the Ci field, for example, if there is noSCell configured with SCell index i. An R field may indicate a reservedbit. The R field may be set to zero or any other value (e.g., for otherpurposes).

A base station may send/transmit, to a wireless device, one or moremessages comprising an SCell timer (e.g., sCellDeactivationTimer). Awireless device may deactivate an SCell, for example, based on (e.g.,after or in response to) an expiry of the SCell timer. An SCellconfigured with an uplink control channel (e.g., a PUCCH SCell) may notbe configured with an SCell timer. Each other SCell (e.g., except forthe SCell configured with an uplink control channel) may run the SCelltimer.

A wireless device may activate an SCell, for example, if the wirelessdevice receives an SCell Activation/Deactivation MAC CE activating theSCell. A wireless device may perform one or more first operations, forexample, based on (e.g., after or in response to) the activating theSCell. The one or more first operations may comprise at least one of:SRS transmissions on/via the SCell; CQI/PMI/RI/CSI-RS resource indicator(CRI) reporting for the SCell; PDCCH monitoring on/via the SCell; PDCCHmonitoring for the SCell (e.g., on/via a PCell or another SCell); and/orPUCCH transmissions on/via the SCell.

The wireless device may start or restart a first SCell timer (e.g.,sCellDeactivationTimer) associated with the SCell, for example, based on(e.g., after or in response to) the activating the SCell. The wirelessdevice may start or restart the first SCell timer in the slot, forexample, in which the SCell Activation/Deactivation MAC CE activatingthe SCell is received. The wireless device may (re-)initialize one ormore suspended configured uplink grants of a configured grant (e.g., aconfigured grant Type 1) associated with the SCell according to a storedconfiguration, for example, based on (e.g., after or in response to) theactivating the SCell. The wireless device may trigger PHR, for example,based on (e.g., after or in response to) the activating the SCell.

A wireless device may deactivate the activated SCell, for example, ifthe wireless device receives an SCell Activation/Deactivation MAC CEdeactivating an activated SCell. The wireless device may deactivate theactivated SCell, for example, if a first SCell timer (e.g.,sCellDeactivationTimer) associated with an activated SCell expires. Thewireless device may stop the first SCell timer associated with theactivated SCell, for example, based on (e.g., after or in response to)the deactivating the activated SCell. The wireless device may clear oneor more configured downlink assignments and/or one or more configureduplink grants of a configured grant (e.g., a configured uplink grantType 2) associated with the activated SCell, for example, based on(e.g., after or in response to) the deactivating the activated SCell.The wireless device may suspend one or more configured uplink grants ofa configured uplink grant (e.g., a configured uplink grant Type 1)associated with the activated SCell and/or flush HARQ buffers associatedwith the activated SCell, for example, based on (e.g., after or inresponse to) the deactivating the activated SCell.

A wireless device may not perform one or more second operations, forexample, if an SCell is deactivated. The one or more second operationsmay comprise at least one of: transmitting SRS on/via the SCell;reporting CQI/PMI/RI/CRI for the SCell; transmitting UL-SCH on/via theSCell; transmitting RACH on/via the SCell; monitoring at least one firstPDCCH on/via the SCell; monitoring at least one second PDCCH for theSCell (e.g., on/via a PCell or another SCell); and/or transmitting aPUCCH on/via the SCell.

A wireless device may restart a first SCell timer (e.g.,sCellDeactivationTimer) associated with an activated SCell, for example,if at least one first PDCCH on the activated SCell indicates an uplinkgrant or a downlink assignment. A wireless device may restart the firstSCell timer (e.g., sCellDeactivationTimer) associated with the activatedSCell, for example, if at least one second PDCCH on/via a serving cell(e.g., a PCell or an SCell configured with PUCCH, i.e., PUCCH SCell)scheduling the activated SCell indicates an uplink grant or a downlinkassignment for the activated SCell. A wireless device may abort anongoing random access procedure on the SCell, for example, if an SCellis deactivated and if there is an ongoing random access procedure on theSCell.

A base station may configure a wireless device with uplink (UL)bandwidth parts (BWPs) and/or downlink (DL) BWPs, for example, to enablebandwidth adaptation (BA) on a PCell. The base station may furtherconfigure the wireless device with at least DL BWP(s) (e.g., there maybe no UL BWPs in the UL) to enable BA on an SCell, for example, if acarrier aggregation is configured for the wireless device. For thePCell, an initial active BWP may be a first BWP used for initial access.For the SCell, a first active BWP may be a second BWP configured for thewireless device to operate on the SCell upon the SCell being activated.

A base station and/or a wireless device may independently switch a DLBWP and/or an UL BWP, for example, in a paired spectrum (e.g., FDD). Abase station and/or a wireless device may simultaneously switch a DL BWPand an UL BWP, for example, in an unpaired spectrum (e.g., TDD).

A base station and/or a wireless device may switch a BWP betweenconfigured BWPs, for example, based on DCI or a BWP inactivity timer. Abase station and/or a wireless device may switch an active BWP to adefault BWP, for example, based on (e.g., after or in response to) anexpiry of a BWP inactivity timer associated with a serving cell if theBWP inactivity timer is configured for the serving cell. The default BWPmay be configured by the network (e.g., via one or more RRC message).

One UL BWP for each uplink carrier and one DL BWP may be active at atime in an active serving cell, for example, for FDD systems ifconfigured with BA. One DL/UL BWP pair may be active at a time in anactive serving cell, for example, for TDD systems. Operating on the oneUL BWP and the one DL BWP (or the one DL/UL pair) may improve wirelessdevice battery consumption efficiencies. BWPs, other than the one activeUL BWP and the one active DL BWP, (e.g., configured for the wirelessdevice and/or that the wireless device may work on) may be deactivated.The wireless device may not monitor PDCCH on/via the deactivated BWPsand/or not send/transmit, on/via the deactivated BWPs, PUCCH, PRACH,and/or UL-SCH. A serving cell may be configured with at most a firstquantity/number (e.g., four or any other quantity/number) of BWPs. Theremay be one active BWP at any point in time, for example, for anactivated serving cell.

A BWP switching for a serving cell may be used to activate an inactiveBWP and/or deactivate an active BWP at a time. In The BWP switching maybe controlled by a PDCCH indicating a downlink assignment and/or anuplink grant. The BWP switching may be controlled by a BWP inactivitytimer (e.g., bwp-InactivityTimer). The BWP switching may be controlledby a base station and/or a wireless device (e.g., a MAC entity of a basestation and/or a wireless device), for example, based on (e.g., after orin response to) initiating a random access procedure. A BWP may beinitially active without receiving a PDCCH indicating a downlinkassignment or an uplink grant, for example, after an addition of anSpCell or activation of an SCell. The active BWP for a serving cell maybe indicated by an RRC message and/or a PDCCH. A DL BWP may be pairedwith a UL BWP, and BWP switching may be common for both UL and DL, forexample, for an unpaired spectrum.

FIG. 22 shows an example of BWP management. BWP management may compriseBWP switching (e.g., switching on an SCell). A wireless device mayreceive one or more RRC messages 2210 comprising parameters of an SCelland one or more BWP configurations associated with the SCell. The one ormore RRC messages 2210 may comprise at least one of: an RRC connectionreconfiguration message (e.g., RRCReconfiguration); an RRC connectionreestablishment message (e.g., RRCRestablishment); and/or an RRCconnection setup message (e.g., RRCSetup). Among the one or more BWPs,at least one BWP may be configured as the first active BWP (e.g., BWP 1shown in FIG. 22), one BWP as the default BWP (e.g., BWP 0 shown in FIG.22). The wireless device may receive an activation indication 2220(e.g., a command, a MAC CE) to activate the SCell (e.g., during n-thslot). The wireless device may start an SCell deactivation timer (e.g.,sCellDeactivationTimer), and start CSI-related actions for the SCell,and/or start CSI-related actions for the first active BWP of the SCell.The wireless device may start monitoring a PDCCH on/via BWP 1, forexample, based on (e.g., after or in response to) activating the SCell.

The wireless device may start or restart a BWP inactivity timer (e.g.,bwp-InactivityTimer) (e.g., during m-th slot), for example, based on(e.g., after or in response to) receiving DCI 2230 indicating a DLassignment on BWP 1. The wireless device may switch back to the defaultBWP (e.g., BWP 0) as an active BWP, for example, if the BWP inactivitytimer expires (e.g., during s-th slot). The wireless device maydeactivate the SCell and/or stop the BWP inactivity timer, for example,if the sCellDeactivationTimer expires.

Using the BWP inactivity timer may further reduce power consumption of awireless device, for example, if the wireless device is configured withmultiple cells and/or one or more cells having a wide bandwidth (e.g., 1GHz). The wireless device may only send/transmit or receive via anarrow-bandwidth BWP (e.g., 5 MHz) on the PCell or an SCell, forexample, if there is no activity on an active BWP. The wireless devicemay determine an expiry of the BWP inactivity timer (e.g., during s-thslot). The wireless device may switch the active BWP (e.g., the BWP 1)to the default BWP (e.g., the BWP 0), for example, based on (e.g., afteror in response to) the .expiry of the BWP inactivity timer.

A wireless device (e.g., a MAC entity of the wireless device) may applynormal operations on an active BWP for an activated serving cellconfigured with a BWP. The normal operations may comprise at least oneof: transmitting on/via a UL-SCH; transmitting on/via a RACH; monitoringa PDCCH; transmitting a PUCCH; and/or receiving a DL-SCH; and/or (re-)initializing any suspended configured uplink grants of a configuredgrant (e.g., configured grant Type 1) according to a storedconfiguration, if any.

A wireless device (e.g., a MAC entity of the wireless device) may notperform one or more operations, for example, on/via an inactive BWP foreach activated serving cell configured with a BWP. The one or moreoperations not performed by the wireless device (e.g., a MAC entity ofthe wireless device) may comprise at least one of: transmitting on/via aUL-SCH; transmitting on/via a RACH; monitoring a PDCCH; transmitting aPUCCH; transmitting an SRS, receiving a DL-SCH; clearing any configureddownlink assignment and/or configured uplink grant of a configured grant(e.g., configured grant Type 2); and/or suspending any configured uplinkgrant of a configured grant (e.g., configured Type 1).

A wireless device may perform BWP switching to a BWP indicated by aPDCCH transmission (e.g., DCI, a PDCCH order, etc.), for example, if thewireless device (e.g., a MAC entity of the wireless device) receives thePDCCH transmission for a BWP switching of a serving cell at time that arandom access procedure associated with this serving cell is notongoing. A bandwidth part indicator field value may indicate an activeDL BWP, from a configured DL BWP set, for DL receptions, for example, ifthe bandwidth part indicator field is configured in DCI format 1_1. Abandwidth part indicator field value may indicate an active UL BWP, froma configured UL BWP set, for UL transmissions, for example, if thebandwidth part indicator field is configured in DCI format 0_1.

A wireless device may be provided with, by a higher layer parameter(e.g., Default-DL-BWP), a default DL BWP among the configured DL BWPs,for example, for a primary cell and/or a secondary cell. The default DLBWP may be the initial active DL BWP, for example, if the wirelessdevice is not provided with a default DL BWP by the higher layerparameter (e.g., Default-DL-BWP).

A wireless device may be provided with a timer value for the primarycell by a higher layer parameter (e.g., bwp-InactivityTimer). Thewireless device may increment the configured timer (if running), forexample, every interval of 1 millisecond for frequency range 1, every0.5 milliseconds for frequency range 2, or any other interval foranother frequency range. The wireless device may increment theconfigured timer, for example, if the wireless device does not detectDCI format 1_1 for a paired spectrum operation or if the wireless devicedoes not detect DCI format 1_1 or DCI format 0_1 for an unpairedspectrum operation during the interval. The wireless device may receivea deactivation indication 2240 (e.g., a command, a MAC CE) fordeactivating one or more SCells. The wireless device may stop the BWPinactivity timer and/or deactivate the one or more SCells, for example,based on (e.g., after or in response to) receiving the deactivationindication 2240.

The wireless device procedures on a secondary cell may be the same as,or similar to, the wireless device procedures on the primary cell, forexample, if the wireless device is configured for the secondary cellwith a higher layer parameter (e.g., Default-DL-BWP) indicating adefault DL BWP among the configured DL BWPs and/or the wireless deviceis configured with a higher layer parameter (e.g., bwp-InactivityTimer)indicating a timer value. The wireless device may perform the same orsimilar procedures, for example, using the timer value for the secondarycell and/or the default DL BWP for the secondary cell. The wirelessdevice may use the indicated DL BWP and the indicated UL BWP on thesecondary cell as the respective first active DL BWP and first active ULBWP on a secondary cell or carrier, for example, if the wireless deviceis configured with, by a higher layer parameter (e.g.,Active-BWP-DL-SCell), a first active DL BWP and with, by a higher layerparameter (e.g., Active-BWP-UL-SCell), a first active UL BWP on thesecondary cell or carrier.

A wireless device may receive an uplink grant dynamically, for example,via a PDCCH or a random access response (RAR). The wireless device mayreceive an uplink grant configured semi-persistently, for example, by aradio resource control (RRC) message. The wireless device maysend/transmit, via the uplink grant, an uplink transport block (TB)on/via an uplink shared channel (UL-SCH). To send/transmit the uplinktransport block, a medium access control (MAC) layer of the wirelessdevice may receive one or more HARQ information from lower layers (e.g.,a PHY layer) of the wireless device. The one or more HARQ informationmay comprise at least one of: a HARQ process identifier (ID); a new dataindicator (NDI); a redundancy version (RV); and/or a transport blocksize (TBS). A wireless device (e.g., a MAC entity of the wirelessdevice) may deliver an uplink grant and one or more associated HARQinformation to a HARQ entity, for example, if the MAC entity of thewireless device has a C-RNTI, a Temporary C-RNTI (TC-RNTI), or aconfigured scheduling RNTI (CS-RNTI), for each PDCCH occasion and foreach serving cell belonging to a time alignment group (TAG) that has arunning timeAlignmentTimer and for each uplink grant received for thePDCCH occasion, if the uplink grant for the serving Cell has beenreceived on the PDCCH for the MAC entity's C-RNTI or TC-RNTI.

A wireless device (e.g., a MAC entity of a wireless device) may set aHARQ Process ID to a HARQ Process ID associated with a PUSCH durationfor each serving cell and each configured uplink grant, if configuredand activated, for example, if the PUSCH duration of the configureduplink grant does not overlap with a second PUSCH duration of an uplinkgrant received on the PDCCH or in an RAR for the serving cell. Thewireless device (e.g., a MAC entity of the wireless device) maydetermine the NDI bit for the corresponding HARQ process to have beentoggled and deliver the configured uplink grant and the associated HARQinformation (e.g., to the HARQ entity), for example, ifconfiguredGrantTimer for the corresponding HARQ process is not running.For a configured uplink grant, a wireless device and/or a base stationmay determine a HARQ Process ID associated with a first symbol of a ULtransmission as: HARQ Process ID=[floor(CURRENT_symbol/periodicity)]modulo nrofHARQ-Processes, whereCURRENT_symbol=(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+slotnumber in the frame×numberOfSymbolsPerSlot+symbol number in the slot),SFN is a system frame number of a frame of the current symbol,numberOfSlotsPerFrame and numberOfSymbolsPerSlot refer to the number ofconsecutive slots per frame and the number of consecutive symbols perslot. A quantity/number of HARQ processes (e.g., nrofHARQ-Processes) maybe a maximum quantity/number of parallel HARQ processes configured by anRRC message. CURRENT_symbol may refer to a symbol index of the firsttransmission occasion of a repetition bundle that takes place.

A wireless device (e.g., a MAC entity of a wireless device) may comprisea HARQ entity for each serving cell with a configured uplink (e.g.,configured with a SUL and/or an NUL). The wireless device (e.g., theHARQ entity of the wireless device) may maintain a number of parallelHARQ processes. Each HARQ process of the number of parallel HARQprocesses may support one TB. The HARQ process may be associated with aHARQ process identifier (ID). For UL transmission with UL grant in anRAR, HARQ process identifier 0 may be used.

FIG. 23 shows an example of a wireless device (e.g., a HARQ entity of awireless device) configured with multiple HARQ processes. A wirelessdevice may send/transmit uplink data to a base station. A HARQ entitymay comprise a number of parallel HARQ processes (e.g., Process #m,Process #n, etc.). Process #m may be indicated/identified with, ordetermined based on, a first HARQ process identifier (e.g., m). Process#n may be indicated/identified with, or determined based on, a secondHARQ process identifier (e.g., n). The wireless device may process TB 1in Process #m (e.g., at step 2311), for example, if the wireless devicetransmits uplink data (e.g., the TB 1) to the base station. The wirelessdevice may process TB 2 in Process #n (e.g., at step 2312), for example,if the wireless device transmits uplink data (e.g., the TB 2) to thebase station. The base station may require a retransmission of TB 1 fromthe wireless device, for example, based on (e.g., after or in responseto) TB 1 being not successfully decoded by the base station. Thewireless device may resend/retransmit at least a portion of the TB 1,for example, based on a HARQ buffer of Process #m (e.g., at step 2321).The base station may indicated to the wireless device a new datatransport block (e.g., TB 3) for Process #n (e.g., at step 2322), forexample, based on (e.g., after or in response to) TB 2 beingsuccessfully decoded. The base station may require a retransmission ofTB 1 from the wireless device, for example, based on (e.g., after or inresponse to) TB 1 being not successfully decoded by the base station.The wireless device may resend/retransmit at least a portion of the TB1, for example, based on a HARQ buffer of Process #m (e.g., at step2331).

A wireless device may receive downlink data from a base station. Asshown in FIG. 23, a HARQ entity may comprise a number of parallel HARQprocesses (e.g., Process #m, Process #n, etc.). Process #m may beindicated/identified with, or determined based on, a first HARQ processidentifier (e.g., m). Process #n may be indicated/identified with, ordetermined based on, a second HARQ process identifier (e.g., n). Awireless device may process TB 1 in Process #m (e.g., at step 2311), forexample, if the wireless device receives downlink data (e.g., the TB 1)from the base station. The wireless device may process TB 2 in Process#n (e.g., at step 2312), for example, if the wireless device receivesdownlink data (e.g., the TB 2) from the base station. The wirelessdevice may store received data of TB1 in a soft buffer of Process #m,for example, based on (e.g., after or in response to) the TB 1 being notsuccessfully decoded by the wireless device. The wireless device maysend/transmit, to the base station, a negative acknowledgement (NACK)associated with the TB 1. The base station may resend/retransmit atleast a portion of the TB 1, for example, based on (e.g., after or inresponse to) receiving the NACK. The wireless device may process TB 1 inProcess #m (e.g., at step 2321), for example, if the wireless devicereceives downlink data (e.g., at least a portion of the TB 1) from thebase station. The wireless device may attempt to decode TB 1, forexample, based on the stored data of TB 1 in the soft buffer andreceived data of retransmission of TB 1. The wireless device maysend/transmit, to the base station, a positive acknowledgement (ACK) forTB 2, for example, based on (e.g., after or in response to) TB 2 beingsuccessfully decoded. The wireless device may deliver decoded data(e.g., a MAC PDU) to a disassembly and demultiplexing entity of thewireless device, for example, based on (e.g., after or in response to)TB 2 being successfully decoded. The base station may send/transmit anew transport block (e.g., TB 3). The wireless device may process thenew transport block (e.g., the TB 3) by using Process #n (e.g., at step2322), for example, based on (e.g., after or in response to) receivingthe new transport block and/or receiving the positive acknowledgement.The wireless device may send/transmit, to the base station, a negativeacknowledgement (NACK) associated with the TB 1. The base station mayresend/retransmit at least a portion of the TB 1, for example, based on(e.g., after or in response to) receiving the NACK. The wireless devicemay process TB 1 in Process #m (e.g., at step 2331), for example, if thewireless device receives downlink data (e.g., at least a portion of theTB 1) from the base station.

A PUSCH transmission parameter (e.g., parameter pusch-AggregationFactor)may indicate a quantity/number of transmissions of a TB within a bundleof a dynamic grant, for example, if a wireless device (e.g., a MACentity of a wireless device) is configured with a PUSCH repetition(e.g., pusch-AggregationFactor>1). The wireless device may perform thePUSH retransmissions (e.g., pusch-AggregationFactor−1 HARQretransmissions) within a bundle, for example, after the initialtransmission. A repetition parameter (e.g., parameter repK) may indicatea quantity/number of transmissions of a TB within a bundle of aconfigured uplink grant, for example, if the wireless device (e.g., aMAC entity of the wireless device) is configured with the repetitionparameter satisfying a first value (e.g., repK>1). HARQ retransmissionsmay follow within a bundle, for example, after the initial transmission.Bundling operation may rely on the HARQ entity for invoking the sameHARQ process for each transmission that is part of the same bundle, forexample, for both dynamic grant and configured uplink grant. Thewireless device may trigger HARQ retransmissions (e.g., within abundle), for example, without waiting for feedback from a previoustransmission according to the PUSCH transmission parameter (e.g.,pusch-AggregationFactor) for the dynamic grant and the repetitionparameter (e.g., the repK) for the configured uplink grant,respectively. Each transmission within a bundle may be a separate uplinkgrant, for example, after the initial uplink grant within a bundle isdelivered to the wireless device (e.g., the HARQ entity of the wirelessdevice).

The wireless device may determine a sequence of redundancy versions. Thewireless device may determine the sequence of redundancy versions, forexample, for each transmission within a bundle of a dynamic grant, basedon one or more fields of DCI carrying the dynamic grant. The wirelessdevice may determine a sequence of redundancy versions, for example, foreach transmission within a bundle of a configured uplink grant, based onone or more configuration parameters in an RRC message.

A wireless device (e.g., a HARQ entity of a wireless device) mayindicate/identify a HARQ process associated with an uplink grant. Forthe indicated/identified HARQ process, the wireless device (e.g., theHARQ entity of the wireless device) may obtain a MAC PDU tosend/transmit from a multiplexing and assembly entity, for example, ifthe received uplink grant is not addressed to a TC-RNTI on PDCCH, and/orif an NDI provided/configured in the associated HARQ information hasbeen toggled compared to an NDI value in the previous transmission ofthe TB of the HARQ process. The wireless device (e.g., the HARQ entityof the wireless device) may deliver/send the MAC PDU, the uplink grant,and/or the HARQ information of the TB to the indicated/identified HARQprocess. The wireless device (e.g., the HARQ entity of the wirelessdevice) may instruct/cause the indicated/identified HARQ process totrigger a new transmission, for example, based on (e.g., after or inresponse to) obtaining the MAC PDU. For the indicated/identified HARQprocess, the wireless device (e.g., the HARQ entity of the wirelessdevice) may deliver/send the uplink grant and/or the HARQ information(e.g., redundancy version) of the TB to the indicated/identified HARQprocess. The wireless device (e.g., the HARQ entity of the wirelessdevice) may instruct/cause the indicated/identified HARQ process totrigger a retransmission, for example, if the received uplink grant isaddressed to a TC-RNTI on PDCCH, and/or if the NDI provided/configuredin the associated HARQ information has not been toggled compared to theNDI value in the previous transmission of the TB of the HARQ process.

A HARQ process may be associated with a HARQ buffer. A wireless devicemay perform a new transmission on/via a resource and with a modulationcoding scheme (MCS) indicated on/via a PDCCH, an RAR, or an RRC message.The wireless device may perform a retransmission on/via a resource and(if provided/configured) with an MCS indicated on/via a PDCCH, or on/viaa same resource and with a same MCS as was used for the lasttransmission attempt within a bundle.

A HARQ process may store the MAC PDU in an associated HARQ buffer, storethe uplink grant received from the HARQ entity, and/or generate atransmission for a TB, for example, if a HARQ entity requests a newtransmission of the TB. The HARQ process may cause storing the uplinkgrant received from the wireless device (e.g., the HARQ entity of thewireless device) and generate a transmission for a TB, for example, ifthe wireless device (e.g., the HARQ entity of the wireless device)requests a retransmission for the TB. The HARQ process mayinstruct/cause the physical layer to generate a transmission signal, forexample, to generate a transmission for a TB. The wireless device (e.g.,the HARQ process and/or the HARQ entity of the wireless device) mayinstruct/cause the physical layer to generate the transmission signal,for example, according to the stored uplink grant if the MAC PDU wasobtained from a buffer (e.g., a Msg3 buffer). The wireless device (e.g.,the HARQ process and/or the HARQ entity of the wireless device) mayinstruct/cause the physical layer to generate the transmission signal,for example, if there is no measurement gap at the time of thetransmission and/or if a retransmission (e.g., in case of aretransmission) does not collide with a transmission for the MAC PDUobtained from the Msg3 buffer.

FIG. 24 shows an example uplink (re)transmission. The uplinkre(transmission) may be based on a HARQ procedure. A base station maysend/transmit to a wireless device, first DCI comprising an uplink grantand/or HARQ information (e.g., at step 2410). The HARQ information maycomprise a HARQ Process ID (e.g., Process ID=k as shown in FIG. 24),and/or a first NDI value (e.g., 1st NDI=1). Before receiving the firstDCI, the wireless device may have a current NDI value (e.g., CurrentNDI=0 as shown in FIG. 24). The wireless device may determine that thefirst NDI has been toggled, for example, based on (e.g., after or inresponse to) receiving the first DCI. The wireless device may determinethat the first NDI has been toggled (e.g., at step 2420), for example,based on the first NDI value (e.g., 1) being different from the currentNDI value (e.g., 0). A wireless device (e.g., a HARQ entity of thewireless device) may obtain a MAC PDU (e.g., from a multiplexing andassembly entity of the wireless device), for example, based on the firstNDI being toggled. The wireless device (e.g., the HARQ entity of thewireless device) may deliver/send the MAC PDU, the uplink grant, and theHARQ information to a HARQ process. The HARQ process may beindicated/identified by, or determined based on, the HARQ process ID(e.g., Process ID=k as shown in FIG. 24). The wireless device (e.g., theHARQ entity of the wireless device) may instruct/cause the HARQ processto trigger a new transmission for a TB comprising the MAC PDU. Thewireless device (e.g., the HARQ process of the wireless device) maycause storing the MAC PDU in an associated HARQ buffer and/or storingthe uplink grant. The wireless device (e.g., the HARQ process of thewireless device) may determine/cause (e.g., instruct/cause a physicallayer of the wireless device to generate) a new transmission for the TB,for example, according to the stored uplink grant. At step 2430, thewireless device (e.g., the physical layer of the wireless device) maysend/transmit the TB (e.g., a first TB), for example, according to thestored uplink grant. The base station may attempt to decode the TB, forexample, based on received data of the TB. The base station maydetermine that the decoding of the TB is unsuccessful (e.g., at step2440). The base station may provide/send/transmit a subsequent uplinkgrant to the wireless device for a retransmission of the TB, forexample, if the base station does not successfully decode the TBsent/transmitted by the wireless device. At step 2440, the base stationmay store the received data of the TB in a buffer (e.g., the soft bufferof a HARQ process), for example, if the base station does notsuccessfully decode the TB transmitted by the wireless device. The basestation may send/transmit second DCI indicating the retransmission(e.g., at step 2450). The second DCI may comprise the same HARQ ProcessID as the first HARQ Process ID, a second uplink grant, an RV value, anda second NDI value (e.g., 2nd NDI=1). The wireless device may determinethat the second NDI is not toggled (e.g., at step 2460), for example,based on the second NDI value (e.g., 1) being equal to the first NDIvalue (e.g., 1). The second NDI value may become the new current NDIvalue. The wireless device (e.g., the HARQ entity of the wirelessdevice) may deliver/send, to a HARQ process indicated/identified by theHARQ process ID (e.g., HARQ Process ID=k), the second uplink grant,and/or the RV value, for example, based on the second NDI not beingtoggled. The wireless device (e.g., the HARQ entity of the wirelessdevice) may instruct/cause the HARQ process to trigger a retransmissionof the TB, for example, based on the second NDI not being toggled. Thewireless device (e.g., the HARQ process of the wireless device) maycause storing of the second uplink grant. The wireless device (e.g., theHARQ process of the wireless device) may determine/cause (e.g.,instruct/cause the physical layer of the wireless device to generate) aretransmission for the TB, for example, according to the second uplinkgrant. At step 2470, the wireless device (e.g., the physical layer ofthe wireless device) may resend/retransmit the TB (e.g., the first TB)according to the second uplink grant. The base station may attempt todecode the TB (e.g., at step 2480), for example, based on the buffereddata and a received data of the retransmitted TB.

A base station may send/transmit second DCI indicating a transmission ofa new TB (e.g., a second TB), for example, if the base stationsuccessfully decodes the TB. The second DCI may comprise a HARQ ProcessID, which may be the same as the first HARQ Process ID, a second uplinkgrant, a RV value, and a second NDI value. A wireless device maydetermine that the second NDI is toggled, for example, based on thesecond NDI value (e.g., 0) being different from the first NDI value(e.g., 1). The second NDI value may become the new current NDI value.The wireless device (e.g., the HARQ entity of the wireless device) mayobtain a second MAC PDU (e.g., from the multiplexing and assemblyentity), for example, based on (e.g., after or in response to) thesecond NDI being toggled. The wireless device (e.g., the HARQ entity ofthe wireless device) may deliver/send the second MAC PDU, the seconduplink grant, and/or second HARQ information to the HARQ process (e.g.,indicated/identified by Process ID=k). The wireless device (e.g., theHARQ entity of the wireless device) may instruct/cause the HARQ processto trigger a new transmission for the second TB comprising the secondMAC PDU. The wireless device (e.g., the HARQ process of the wirelessdevice) may cause storing of the second MAC PDU in a HARQ buffer of theHARQ process and/or storing of the second uplink grant. The wirelessdevice (e.g., the HARQ process of the wireless device) maydetermine/cause (e.g., instruct/cause the physical layer of the wirelessdevice to generate) a new transmission for the second TB, for example,according to the second uplink grant. The wireless device (e.g., thephysical layer of the wireless device) may send/transmit the second TB,for example, based on the instruction and according to the second uplinkgrant.

A wireless device may receive one or more downlink assignments. The oneor more downlink assignment may be received on/via a PDCCH. The one ormore downlink assignments may indicate that there is a transmissionon/via a downlink shared channel (DL-SCH) for the wireless device (e.g.,a MAC entity of the wireless device). The one or more downlinkassignments may indicate HARQ information. The HARQ information maycomprise at least one of: a HARQ process identifier (ID); an NDI; an RV;and/or a TBS. The wireless device (e.g., the MAC entity of the wirelessdevice) may indicate a presence of a downlink assignment anddeliver/send associated HARQ information to the HARQ entity, forexample, if the wireless device (e.g., the MAC entity of the wirelessdevice) has a C-RNTI, TC-RNTI or CS-RNTI, for each PDCCH occasion duringwhich it monitors a PDCCH and for each serving cell. The wireless device(e.g., the MAC entity of the wireless device) may indicate the presenceof a downlink assignment and deliver/send the associated HARQinformation (e.g., to the HARQ entity of the wireless device), forexample, if the downlink assignment for the PDCCH occasion and theserving cell is received on the PDCCH for the MAC entity's C-RNTI orTC-RNTI. The wireless device (e.g., the MAC entity of the wirelessdevice) may determine an NDI for a corresponding HARQ process not tohave been toggled and indicate the presence of a downlink assignment anddeliver/send the associated HARQ information (e.g., to the HARQ entityof the wireless device), for example, if the downlink assignment for thePDCCH occasion is received on/via the PDCCH for the MAC entity'sCS-RNTI. If the NDI in the received HARQ information is 1 (or any othervalue), the wireless device (e.g., the MAC entity of the wirelessdevice) may: determine the NDI for the corresponding HARQ process not tohave been toggled, indicate the presence of a downlink assignment,and/or deliver/send the associated HARQ information (e.g., to the HARQentity of the wireless device). The wireless device (e.g., the MACentity of the wireless device) may store the downlink assignment and theassociated HARQ information as configured downlink assignment and/orinitialize the configured downlink assignment to start in the associatedPDSCH duration and recur, for example, if the downlink assignment forthe PDCCH occasion is received on/via the PDCCH for the CS-RNTIassociated with the wireless device (e.g., the CS-RNTI of the MACentity). The wireless device (e.g., the MAC entity of the wirelessdevice) may cause storing of the downlink assignment and the associatedHARQ information as the configured downlink assignment and/or mayinitialize the configured downlink assignment to start in the associatedPDSCH duration and recur, for example, if the NDI in the received HARQinformation is 0 (or any other value) and/or if PDCCH content indicatesan SPS activation.

The wireless device (e.g., the MAC entity of the wireless device) mayreceive a TB according to a configured downlink assignment. The wirelessdevice may instruct/cause (e.g., the physical layer of the wirelessdevice) to receive, in the PDSCH duration, the TB on/via the DL-SCH, forexample, for a serving cell and the configured downlink assignment (ifconfigured and activated) and/or if a PDSCH duration of the configureddownlink assignment does not overlap with a second PDSCH duration of adownlink assignment received on/via a PDCCH. The wireless device (e.g.,the MAC entity of the wireless device) may deliver/send the TB to theHARQ entity of the wireless device. The wireless device (e.g., the MACentity of the wireless device) may set a HARQ Process ID to the HARQProcess ID associated with the PDSCH duration. The wireless device(e.g., the MAC entity of the wireless device) may determine the NDI bitfor the corresponding HARQ process to have been toggled. The wirelessdevice (e.g., the MAC entity of the wireless device) may indicate thepresence of the configured downlink assignment and deliver/send thestored HARQ information (e.g., to the HARQ entity).

A wireless device and/or a base station may determine an HARQ processfor a configured downlink assignment and/or an uplink grant. For aconfigured downlink assignment, a wireless device and/or a base stationmay determine a HARQ Process ID associated with a slot in which thedownlink transmission starts as: HARQ Process ID=[floor(CURRENT_slot×10/(numberOfSlotsPerFrame×periodicity))] modulonrofHARQ-Processes, where CURRENT_slot=[(SFN×numberOfSlotsPerFrame)+slotnumber in the frame], SFN may be a system frame number of the slot, andnumberOfSlotsPerFrame may refer to the number of consecutive slots perframe. A quantity/number of HARQ processes (e.g., nrofHARQ-Processes)may be the maximum quantity/number of parallel HARQ processes configuredby an RRC message. For a downlink assignment (dynamic) received in DCIvia a PDCCH, the wireless device may obtain the HARQ Process IDassociated with a TB from a HARQ Process ID field of the DCI. A basestation may set a value of the HARQ Process ID field of the DCIindicating a HARQ Process ID for the associated TB.

A wireless device (e.g., the MAC entity of the wireless device) maycomprise a HARQ entity for each serving cell, which may maintain anumber of parallel HARQ processes (e.g., as shown in FIG. 23). Each HARQprocess may be associated with a HARQ process identifier (ID). Thewireless device (e.g., the HARQ entity of the wireless device) maydirect/deliver/send HARQ information and associated TBs received on/viathe DL-SCH to corresponding HARQ processes. A HARQ process may supportone TB, for example, if a physical layer of the wireless device is notconfigured for downlink spatial multiplexing. The HARQ process maysupport one or two TBs, for example, if the physical layer is configuredfor downlink spatial multiplexing.

A PDSCH parameter (e.g., the parameter pdsch-AggregationFactor) mayindicate a quantity/number of transmissions of a TB. The PDSCH parametermay indicate the quantity/number of transmissions of a TB (e.g., withina bundle of the downlink assignment), for example, if the wirelessdevice (e.g., the MAC entity of the wireless device) is configured withthe PDSCH parameter satisfying a first value (e.g.,pdsch-AggregationFactor>1). Bundling operation may rely on the wirelessdevice (e.g., the HARQ entity of the wireless device) for invoking thesame HARQ process for each transmission that is part of the same bundle.The base station may perform a quantity/number of (e.g.,pdsch-AggregationFactor—1) HARQ retransmissions within a bundle, forexample, after the initial transmission.

The wireless device (e.g., the MAC entity of the wireless device) mayallocate TB(s) received from the physical layer and the associated HARQinformation to the HARQ process indicated by the associated HARQinformation, for example, if a downlink assignment has been indicated.The wireless device (e.g., the HARQ process of the wireless device) mayreceive one or two TBs (e.g., in case of downlink spatial multiplexing),or any other quantity of TBs, and/or may receive the associated HARQinformation (e.g., from the HARQ entity of the wireless device), forexample, if a transmission takes place for a HARQ process. For eachreceived TB and the associated HARQ information, the wireless device(e.g., the HARQ process of the wireless device) may determine atransmission to be a new transmission, for example, if an NDI has beentoggled compared to a value of a previous received transmissioncorresponding to the TB, and/or if the transmission is the firstreceived transmission for the TB (e.g., if there is no previous NDI forthe TB); otherwise the HARQ process may determine the transmission to bea retransmission. The wireless device (e.g., the MAC entity of thewireless device) may attempt to decode received data of the TB, forexample, based on the transmission being a new transmission. Thewireless device (e.g., the MAC entity of the wireless device) maycombine (e.g., instruct/cause the physical layer to combine) thereceived data with the data currently in the soft buffer for the TB andattempt to decode the combined data, for example, based on thetransmission being a retransmission, if the data for the TB has not beensuccessfully decoded. The wireless device may not successfully decodethe TB, for example, if checking cyclic redundancy check (CRC) bits ofthe received data fails. The wireless device (e.g., the MAC entity ofthe wireless device) may deliver/send the decoded MAC PDU (e.g., to adisassembly and demultiplexing entity of the wireless device), forexample, if the data which the wireless device (e.g., the MAC entity)attempted to decode is successfully decoded for the TB, and/or if thedata for the TB was successfully decoded before; otherwise the wirelessdevice (e.g., the MAC entity) may replace (e.g., instruct/cause thephysical layer to replace) the data in a buffer (e.g., the soft bufferfor the TB) with the data which the wireless device (e.g., the MACentity) attempted to decode. The wireless device (e.g., the MAC entity)may generate (e.g., instruct/cause the physical layer to generate)acknowledgement(s) for the data in the TB.

FIG. 25 shows an example downlink (re)transmission. The downlink(re)transmission mechanism may be based on a HARQ procedure. A basestation may send/transmit, to a wireless device, first DCI comprising adownlink assignment and HARQ information (e.g., at step 2510). The HARQinformation may comprise a HARQ process ID (e.g., Process ID=k as shownin FIG. 25), a first NDI value (e.g., 1st NDI=1), and/or the like. Thewireless device (e.g., the physical layer of the wireless device) mayreceive the data of a first TB, for example, based on the downlinkassignment. Before receiving the first DCI, the wireless device may havea current NDI value (e.g., Current NDI=0 as shown in FIG. 25). Thewireless device may determine that the first NDI has been toggled, forexample, based on (e.g., after or in response to) receiving the firstDCI. The wireless device may determine that the first NDI has beentoggled (e.g., at step 2520), for example, based on the first NDI value(e.g., 1) being different from the current NDI value (e.g., 0). Thewireless device may receive the first TB (e.g., at step 2530). Thewireless device (e.g., the MAC entity of the wireless device) maydetermine a transmission of the first TB to be a new transmission, andattempt to decode the received data of the first TB, for example, basedon the first NDI being toggled. The wireless device (e.g., the MACentity of the wireless device) may not successfully decode the receiveddata (e.g., at step 2540). The wireless device (e.g., the MAC entity ofthe wireless device) may replace (e.g., instruct/cause the physicallayer of the wireless device to replace) a soft buffer for the first TBwith the data which the wireless device (e.g., the MAC entity of thewireless device) attempted to decode (e.g., at step 2540), for example,based on (e.g., after or in response to) not successfully decoding thereceived data. The wireless device (e.g., the MAC entity of the wirelessdevice) may generate (e.g., instruct/cause the physical layer togenerate) a negative acknowledgement (NACK) for the data in the firstTB. The wireless device may send/transmit the NACK to the base station(e.g., at step 2550), for example, based on (e.g., after or in responseto) not successfully decoding the received data. The base station maysend/transmit second DCI indicating a retransmission of the first TB(e.g., at step 2560), for example, based on (e.g., after or in responseto) receiving the NACK. The second DCI may comprise a HARQ process ID,which may be the same as the first HARQ process ID, a second downlinkassignment, an RV value, and/or a second NDI value (e.g., 2nd NDI=1).The wireless device may determine that the second NDI is not toggled(e.g., at step 2570), for example, based on the second NDI value(e.g., 1) being equal to the first NDI value (e.g., 1). The second NDIvalue may become the new current NDI value. The wireless device (e.g.,the physical layer of the wireless device) may receive the data of theretransmitted first TB (e.g., at step 2580), for example, via the seconddownlink assignment. The wireless device (e.g., the MAC entity of thewireless device) may determine the transmission via the second downlinkassignment to be a retransmission of the first TB, for example, based onthe second NDI not being toggled. The wireless device may attempt todecode the first TB (e.g., at step 2590), for example, based on thenewly received data of the first TB and/or the current data in a buffer(e.g., the soft buffer associated with the HARQ processindicated/identified by HARQ Process ID k).

The wireless device (e.g., the MAC entity of the wireless device) maysuccessfully decode the received data of the first TB. The wirelessdevice (e.g., the MAC entity of the wireless device) may deliver/send adecoded data (e.g., a MAC PDU) to a disassembly and demultiplexingentity of the wireless device, for example, based on (e.g., after or inresponse to) successfully decoding the received data. The wirelessdevice (e.g., the MAC entity of the wireless device) may generate (e.g.,instruct/cause the physical layer to generate) an acknowledgement (ACK)for the data in the first TB. The wireless device may send/transmit, tothe base station, the ACK for the first TB.

The wireless device may process downlink TBs associated with multipleHARQ processes in a way of in-order processing (e.g., a pipelineprocessing). The wireless device may process the downlink TBs, forexample, if the wireless device is capable of in-order processing andthe multiple HARQ processes are supported in the wireless device. Forany two HARQ processes (e.g., HARQ process A and HARQ process B) for agiven cell, the wireless device may not be required to send/transmitsecond HARQ-ACK information for the HARQ process B beforesending/transmitting first HARQ-ACK information for the HARQ process A,for example, in in-order processing. The wireless device may not berequired to send/transmit the second HARQ-ACK information for the HARQprocess B before sending/transmitting the first HARQ-ACK information forthe HARQ process A, for example, if a scheduled unicast PDSCHtransmission for the HARQ process A comes before a scheduled unicastPDSCH transmission for the HARQ process B. In a pipeline processing, awireless device may process a first TB associated with a HARQ process Aand may send/transmit first HARQ-ACK information for the first TB beforeprocessing the second TB. The wireless device may process the second TBassociated with HARQ process B and generate second HARQ-ACK informationfor the second TB, for example, after processing the first TB andsending/transmitting the first HARQ-ACK information for the first TB.The in-order processing may reduce implementation complexity of thewireless device.

A wireless device may be required to be capable of out-of-orderprocessing (e.g., to reduce HARQ feedback delay and/or data transmissionlatency), for example, if the wireless device supports a low-latencydata service. A low-latency data service may comprise at least one of:ultra-reliable low-latency communication (URLLC), industrial internet ofthings (IOT), vehicle to everything (V2X) communication, enhanced URLLC,and/or any other communications such as those compatible with one ormore 3GPP releases or any other communication technologies.

FIG. 26A shows an example of out-of-order processing. Out-of-orderprocessing may comprise an in-order scheduling and an out-of-order HARQprocessing. As shown in FIG. 26A, a wireless device may receive at leasta portion of first DCI scheduling a first TB (e.g., at or during a timeperiod T1) before receiving at least a portion of second DCI schedulinga second TB (e.g., at or during a time period T2). The first DCI and/orthe second DCI, comprising a CRC scrambled by a C-RNTI, may indicate adynamic downlink scheduling (or any other scheduling). The first DCIand/or the second DCI, comprising a CRC scrambled by a CS-RNTI, mayindicate a semi-persistent scheduling (or any other scheduling). Thefirst TB may be associated with a first HARQ process. The second TB maybe associated with a second HARQ process. The first DCI may indicate afirst HARQ process ID of the first HARQ process. The second DCI mayindicate a second HARQ process ID of the second HARQ process. Thewireless device may receive at least a portion of the first TB (e.g., ator during a time period T3) before receiving at least a portion of thesecond TB (e.g., at or during a time period T4). The first and second TBmay be referred to as in-order scheduled, for example, because the firstTB scheduled by the first received first DCI may be received before thesecond TB scheduled by the second received second DCI, which may bereceived after receiving the first DCI. TBs may be referred to asin-order scheduled if the TBs are scheduled to be received in the sameorder that their respective scheduling DCI messages are received. Asshown in FIG. 26A, the wireless device may send/transmit an uplinksignal comprising second HARQ-ACK information for the second TB (e.g.,at or during a time period T5) before sending/transmitting an uplinksignal comprising first HARQ-ACK information for the first TB (e.g., ator during a time period T6). The first and second HARQ-ACK informationmay be referred to as out-of-order HARQ processed, for example, becausethe second HARQ-ACK information for the second TB scheduled by thesecond DCI may be sent/transmitted before the first HARQ-ACK informationfor the first TB scheduled by the first DCI. HARQ-ACK information may bereferred to as out-of-order HARQ processed if the HARQ-ACK informationis sent/transmitted in a different order than the DCI messages, whichschedule their respective associated TBs, are received. HARQ-ACKinformation may be out-of-order HARQ processed if the HARQ-ACKinformation is sent/transmitted in a different order than theirrespective associated TBs are received. By using in-order scheduling andout-of-order HARQ processing, advantages may be achieved such as a basestation and a wireless device may improve/reduce latency (e.g., reduceURLLC transmission latency).

FIG. 26B shows an example of out-of-order processing. An in-orderscheduling may reduce scheduling flexibility of a base station. A basestation and/or a wireless device may implement an out-of-orderscheduling, for example, to improve scheduling flexibility and reduceURLLC transmission latency. The out-of-order processing may comprise anout-of-order scheduling and/or an out-of-order HARQ processing. Theout-of-order processing may comprise an out-of-order scheduling and anin-order HARQ processing. The out-of-order processing may comprise anin-order scheduling and an out-of-order HARQ processing. As shown inFIG. 26B, a wireless device may receive at least a portion of first DCIscheduling a first TB (e.g., at or during a time period T1) beforereceiving at least a portion of second DCI scheduling a second TB (e.g.,at or during a time period T2). The first TB may be associated with afirst HARQ process. The second TB may be associated with a second HARQprocess. The first DCI may indicate a first HARQ process ID of the firstHARQ process. The second DCI may indicate a second HARQ process ID ofthe second HARQ process. The wireless device may receive at least aportion of the second TB (e.g., at or during a time period T3) beforereceiving at least a portion of the first TB (e.g., at or during a timeperiod T4). The first and second TB may be referred to as out-of-orderscheduled because the first TB scheduled by the first received first DCIis received after the second TB scheduled by the second received secondDCI, which was received after receiving the first DCI. As shown in FIG.26B, the wireless device may send/transmit second HARQ-ACK informationfor the second TB (e.g., at or during a time period T5), for example,before sending/transmitting first HARQ-ACK information for the first TB(e.g., at or during a time period T6). The first and second HARQ-ACKinformation may be referred to as out-of-order HARQ processed. The firstand second HARQ-ACK information may be out-of-order HARQ processed, forexample, because the second HARQ-ACK information for the second TBscheduled by the second DCI may be sent/transmitted before the firstHARQ-ACK information for the first TB scheduled by the first DCI and thefirst DCI may be received before receiving the second DCI. HARQ-ACKinformation may be referred to as out-of-order HARQ processed, forexample, if the order of sending/transmitting the HARQ-ACK informationassociated with the first TB (and/or the first DCI) and the HARQ-ACKinformation associated with the second TB (and/or the second DCI) isdifferent from the order of receiving the first DCI and the second DCI.

HARQ-ACK information may be out-of-order HARQ processed. HARQ-ACKinformation may be out-of-order HARQ processed, for example, if theorder of sending/transmitting the HARQ-ACK information associated withthe first TB and the HARQ-ACK information associated with the second TBis different from the order of receiving their respective associatedTBs. The wireless device may send/transmit first HARQ-ACK informationfor the first TB (e.g., at or during a time period T5), for example,before sending/transmitting second HARQ-ACK information for the secondTB (e.g., at or during a time period T6). The first and second HARQ-ACKinformation may be referred to as out-of-order HARQ processed, forexample, because the first HARQ-ACK information for the first TBscheduled by the first DCI may be sent/transmitted before the secondHARQ-ACK information for the second TB scheduled by the second DCI andthe second TB may be received before receiving the first TB. By usingout-of-order scheduling and/or out-of-order HARQ processing, a basestation and a wireless device may improve scheduling flexibility and/ortransmission latency.

An out-of-order scheduling may be similarly implemented as anout-of-order grant in uplink transmission. A wireless device may receivefirst DCI indicating a first uplink TB transmission via a first PUSCHand second DCI indicating a second uplink TB transmission via a secondPUSCH. The first uplink TB may be associated with a first HARQ process.The second uplink TB may be associated with a second HARQ process. Thewireless device may receive the first DCI before receiving the secondDCI. The wireless device may be required to transmit the second TB viathe second PUSCH before transmitting the first TB via the first PUSCH.Transmitting the second TB before transmitting the first TB, andreceiving the first DCI before the second DCI, may be referred to as anout-of-order grant. The wireless device may be capable of processing anout-of-order grant. The wireless device may reduce uplink transmissionlatency, for example, if the out-of-order grant is used forsending/transmitting an urgent data packet (e.g., URLLC, industrial IOT,V2X communication, sidelink communication, or enhanced URLLC in future3GPP releases or any other communications). As further described herein,out-of-order processing, out-of-order scheduling, out-of-order grant,and/or out-of-order HARQ processing may be performed for a configurationof multiple TRPs, a configuration of different CORESET groups, aconfiguration of multiple antenna panels, and/or a configuration of anyother multiple/different resources, devices, functions, etc.

FIG. 27 shows an example of a prioritization for HARQ processing.Out-of-order processing may increase implementation complexity of awireless device and/or a base station. The wireless device mayprioritize processing of one TB over another (e.g., by dropping theprocessing of a low-priority TB), for example, to reduce theimplementation complexity of the wireless device. Droppinginformation/data or the dropping the processing of information/data maycomprise, for example, at least one of: ignoring the information/data;stopping processing the information/data; avoiding processing theinformation/data; not storing the information/data; not configuring toreceive the information/data; not receiving the information/data; notscheduling to receive the information/data; skipping allocating theinformation/data to a resource/process; skipping decoding theinformation/data; skipping generating an ACK or NACK for theinformation/data; not sending (e.g., dropping) a HARQ-ACK, refrainingfrom a channel estimation associated with the information/data;refraining from decoding and/or demodulating the information/data;refraining from buffering received data for the information/data; and/orclearing a buffered data associated with the information/data, etc. Asshown in FIG. 27, a wireless device may receive first DCI scheduling afirst TB via a first PDSCH (e.g., at or during a time period T1). Thewireless device may receive second DCI scheduling a second TB via asecond PDSCH (e.g., at or during a time period T2). The first DCI mayindicate a first HARQ-ACK transmission timing for the first TBassociated with a first HARQ process (e.g., HARQ process x). The secondDCI may indicate a second HARQ-ACK transmission timing for the second TBassociated with a second HARQ process (e.g., HARQ process y). Thescheduling of the first TB and the second TB may be an in-orderscheduling (e.g., as shown in FIG. 27) or an out-of-order scheduling.The wireless device may determine a second HARQ-ACK informationtransmission for the second TB is out-of-order compared with a firstHARQ-ACK information transmission for the first TB, for example, basedon the first DCI received before receiving the second DCI. Theout-of-order HARQ processing may comprise sending/transmitting thesecond HARQ-ACK information for the second TB (e.g., at or during a timeperiod T5) before sending/transmitting the first HARQ-ACK informationfor the first TB (e.g., at or during a time period T6). The wirelessdevice may drop and/or not process the first TB (e.g., at or during atime period T3), for example, based on the determining that the secondHARQ-ACK information transmission is out-of-order compared with thefirst HARQ-ACK information transmission. Dropping and/or not processingthe first TB may comprise, for example, at least one of: ignoring thefirst TB; stopping processing the first TB; avoiding processing thefirst TB; not storing the first TB; not configuring to receive the firstTB; not receiving the first TB; not scheduling to receive the first TB;skipping allocating the first TB to a resource/process; skippingdecoding the first TB; skipping generating an ACK or NACK for the firstTB; refraining from a channel estimation of the first PDSCH based on aDM-RS of the first PDSCH; refraining from decoding and/or demodulatingthe first TB; refraining from buffering the received data for the firstTB; and/or clearing a buffered data for the first HARQ process, etc. Thewireless device may receive and/or process the second TB via the secondPDSCH (e.g., at or during a time period T4), for example, based ondropping and/or not processing the first TB. The wireless device maygenerate second HARQ-ACK information for the second TB and send/transmitthe second HARQ-ACK information to the base station (e.g., at or duringthe time period T5). The second HARQ-ACK information may comprise apositive acknowledgement, for example, based on (e.g., after or inresponse to) successfully decoding the second TB. The second HARQ-ACKinformation may comprise a negative acknowledgement, for example, basedon (e.g., after or in response to) unsuccessfully decoding the secondTB. The wireless device may generate first HARQ-ACK information for thefirst TB and may send/transmit the first HARQ-ACK information to thebase station (e.g., at or during the time period T6) (not shown). Thefirst HARQ-ACK information may comprise a negative acknowledgment, forexample, based on (e.g., after or in response to) dropping the receptionof the first TB. Dropping processing of a low-priority data packet forthe purpose of reducing processing latency for a high-priority datapacket may simplify implementation of a wireless device, reduce powerconsumption of the wireless device, and/or reduce cost of the wirelessdevice, for example, if out-of-order processing (e.g., out-of-orderscheduling, out-of-order HARQ processing, and/or out-of-order grant) issupported. Omitting to specify/indicate whether processing of alow-priority data packet is dropped may result in misalignment of thewireless device's behavior on the processing of the low-priority datapacket, increase signaling overhead, and/or reduce system throughput.Dropping processing of a low-priority data packet may bespecified/indicated to align with a base station regarding the behaviorof the wireless device for the low-priority data packet, for example, ifout-of-order processing is supported.

A wireless device may drop processing of a low-priority TB, for example,in at least some types of communications (e.g., communications bywireless devices compatible with 3GPP Release [15], earlier/later 3GPPreleases, and/or any other access technologies). A wireless device maydrop processing of a low-priority TB (e.g., a first TB as shown in FIG.26A, FIG. 26B, and FIG. 27), for example, if the wireless deviceperforms out-of-order processing. A wireless device may automaticallysupport out-of-order HARQ processing, for example, if the wirelessdevice is capable of carrier aggregation and/or MIMO processing. Awireless device may process the low-priority TB (e.g., the first TB asshown in FIG. 26A, FIG. 26B, and FIG. 27), for example, if the wirelessdevice is performing the out-of-order processing. A wireless device mayprocess the low-priority TB, in addition to processing the high-priorityTB, for example, if the wireless device is capable of processing anout-of-order scheduling and/or an out-of-order HARQ-ACK feedback (e.g.,by using carrier aggregation capability and/or MIMO capability).Reliance (e.g., overreliance) on CA and/or MIMO capability to supportout-of-order processing may increase device implementation cost and/orpower consumption (e.g., if a low-price wireless device may not becapable of CA processing and/or MIMO processing). Dropping processing ofa low-priority TB, without considering some cases if a low-priority TBrequires less processing complexity and/or time than a high-priority TB,may reduce system throughput. A wireless device may not be required tosend/transmit a HARQ-ACK feedback for a TB. A wireless device may beallowed to delay a HARQ-ACK feedback for the TB. The HARQ-ACK feedbacknot being required, or the HARQ-ACK feedback being allowed to bedelayed, may relax out-of-order processing. Dropping processing of thelow-priority TB without considering a HARQ-ACK processing requirementfor a TB may result in a reduction of system throughput. Processing ofthe low-priority TB using CA capability and/or MIMO capability withoutconsidering a HARQ-ACK processing requirement for the low-priority TBmay result in a reduction of system throughput, and/or increase powerconsumption or implementation cost. As described further herein,out-of-order processing may be improved, for example, if a HARQ-ACKprocessing requirement for a TB is relaxed. Various configurationsdescribed herein may improve system throughput and/or data transmissionlatency, or reduce power consumption of the wireless device and/orimplementation cost.

FIG. 28 shows an example of out-of-order processing. A wireless devicemay receive (e.g., at or during a first time interval T1) at least aportion of first DCI indicating a PDSCH resource for transmission of afirst TB. A time interval may be a symbol in a slot, a slot in a radioframe, a mini-slot in a slot/radio frame, or any other timeinterval/duration/period. The first DCI may indicate a time of thetransmission of the first TB. The first DCI may indicate that at least aportion of the transmission of the first TB occurs at or during a thirdtime interval T3. The first DCI may indicate a first HARQ process (e.g.,HARQ process x) associated with the first TB. The first DCI may indicatea first HARQ-ACK feedback timing value for the first TB. The firstHARQ-ACK feedback timing value may indicate that the wireless device isrequired to transmit/provide the first HARQ-ACK information at or duringa sixth time interval T6. The wireless device may receive (e.g., at orduring a second time interval T2) at least a portion of second DCIindicating a PDSCH resource for transmission of a second TB. The secondDCI may indicate a time of the transmission of the second TB. The secondDCI may indicate that at least a portion of the transmission of thesecond TB occurs at or during a fourth time interval T4. The second DCImay indicate a second HARQ process (e.g., HARQ process y) associatedwith the second TB. The second DCI may indicate a second HARQ-ACKfeedback timing value for the second TB. The second HARQ-ACK feedbacktiming value may indicate that the wireless device is required totransmit/provide the second HARQ-ACK information at or during a fifthtime interval T5. The second time interval T2 may occur a number of timeintervals after the first time interval T1. The fourth time interval T4may occur a number of time intervals after the third time interval T3.The sixth time interval T6 may occur a number of time intervals afterthe fifth time interval T5. The second TB may arrive before the firstTB, for example, if an out-of-scheduling is supported (e.g., the secondTB may arrive at or during the third time interval T3 and the first TBmay arrive at or during the fourth time interval T4). The wirelessdevice may, based on the first DCI and the second DCI, determine that asecond HARQ-ACK feedback for the second TB is out-of-order, comparedwith the first HARQ-ACK feedback for the first TB. The wireless devicemay determine that the second HARQ-ACK feedback for the second TB isout-of-order, for example, based on the second HARQ-ACK feedback beingscheduled to be sent/transmitted before transmitting the first HARQ-ACKfeedback. The first TB may be referred to as a low-priority TB. Thesecond TB may be referred to as a high-priority TB.

The wireless device may determine to drop a transmission of the secondHARQ-ACK feedback for the second TB. The wireless device may determinethat the second HARQ-ACK feedback for the second TB is not required. Thewireless device may determine to drop a transmission of the secondHARQ-ACK feedback for the second TB, for example, based on the second TBbeing scheduling by a group common DCI (e.g., a group common DCI withCRC scrambled by an RNTI addressed to a group of wireless devices). Thewireless device may determine to drop a transmission of the secondHARQ-ACK feedback for the second TB, for example, based on the second TBof a random access procedure (e.g., Msg 4 1314 for a random accessprocedure). The wireless device may determine to drop a transmission ofthe second HARQ-ACK feedback for the second TB, for example, based on atime gap between the fourth time interval T4 and the fifth time intervalT5 being less than a HARQ-ACK processing time threshold (e.g., Tproc,1).The HARQ-ACK processing time threshold may be determined, for example,based on a PDSCH processing time capability parameter and one or moresystem configuration parameters configured in an RRC message. The RRCmessage may comprise at least one of: ServingCellConfig IE;CellGroupConfig IE; an RRCSetup message; and/or an RRCReconfigurationmessage. The PDSCH processing time capability parameter may be a PDSCHprocessing time (N1) for a PDSCH processing capability type (e.g., type1, type 2, or the like) for a numerology index (u=0, 1, 2, or 3). Theone or more system configuration parameters may comprise: a numerologyindex; an OFDM signal sample length (Tc=1/(Δfmax*Nf), whereΔfmax=480*10{circumflex over ( )}3 Hz and Nf=4096); a number value (d1,1being one of 0, 1, 2, . . . , m, m is an integer) based on a PDSCH DM-RSlocation and/or a number of PDSCH OFDM symbols in a slot. Tproc,1=(N1+d1,1)(2048+144)*k*2{circumflex over ( )}(−u)*Tc, where k=64, forexample. A wireless device may determine to drop a transmission of thesecond HARQ-ACK feedback for the second TB, for example, based on: thesecond DCI not comprising a HARQ-ACK feedback timing value and/or theHARQ-ACK feedback timing value of the second DCI being set to apredefined value.

The wireless device may process the first TB (e.g., at or during thethird time interval T3) and/or process the second TB (e.g., at or duringthe fourth time interval T4), for example, based on (e.g., after or inresponse to) determining dropping transmission of the second HARQ-ACKfeedback for the second TB. Processing the first TB may comprise atleast one of: receiving data symbols of the first TB via the firstPDSCH, performing a channel estimation for the first TB based on a DM-RSof the first PDSCH, demodulating and decoding of the received datasymbols of the first TB, buffering the received data symbols for thefirst TB, and/or generating the first HARQ-ACK information for the firstTB. The wireless device may process the second TB. Processing the secondTB may comprise at least one of: receiving data symbols of the second TBvia the second PDSCH, performing a channel estimation for the second TBbased on a DM-RS of the second PDSCH, demodulating and decoding of thereceived data symbols of the second TB, and/or not generating the secondHARQ-ACK information for the second TB. The wireless device may nottransmit (e.g., may refrain from transmitting) the second HARQ-ACKinformation for the second TB (e.g., at or during the fifth timeinterval T5), for example, based on processing the second TB. Thewireless device may send/transmit the first HARQ-ACK information for thefirst TB (e.g., at or during the sixth time interval T6), for example,based processing the first TB. The wireless device may process bothhigh-priority TB and low-priority TB (e.g., without dropping theprocessing of the low-priority TB), for example, based on (e.g., afteror in response to) determining dropping of a HARQ-ACK feedback for thehigh-priority TB. The wireless device may process the high-priority TBand/or drop processing of the low-priority TB, for example, based on(e.g., after or in response to) determining transmitting of anout-of-order HARQ feedback for the high-priority TB. Dropping (or notdropping) processing of a low-priority TB based on determining whetherto transmit an out-of-order HARQ feedback for a high-priority TB mayreduce misalignment between a base station and a wireless deviceregarding processing of the low-priority TB and/or may improve systemthroughput and/or data transmission latency. As described furtherherein, out-of-order processing, out-of-order scheduling, out-of-ordergrant, and/or out-of-order HARQ processing may be performed for aconfiguration of multiple TRPs, a configuration of multiple CORESETgroups, a configuration of multiple antenna panels, and/or aconfiguration of any other multiple/different resources, devices,functions, etc.

FIG. 29 shows an example of out-of-order processing. The out-of-orderprocessing may comprise out-of-order HARQ processing, for example, in aconfiguration in which semi-persistent scheduling is supported. Awireless device may receive (e.g., at or during a first time intervalT1) at least a portion of first DCI indicating a PDSCH resource fortransmission of a first TB. The first DCI may indicate a time of thetransmission of the first TB. The first DCI may indicate that thetransmission of at least a portion of the first TB occurs at or during athird time interval T3. The first DCI may indicate a first HARQ process(e.g., HARQ process x) associated with the first TB. The first DCI mayindicate a first HARQ-ACK feedback timing value for the first TB. Thefirst HARQ-ACK feedback timing value may indicate that the wirelessdevice is required to send/transmit the first HARQ-ACK information at orduring a sixth time interval T6.

The wireless device may receive (e.g., at or during a second timeinterval T2 at least a portion of second DCI indicating a plurality ofPDSCH resources for transmission repetitions of a second TB. The secondDCI may indicate a first transmission of the second TB with a firstredundancy version (RV) and/or a second transmission of the second TBwith a second RV. The second DCI may indicate that the firsttransmission of the second TB with the first RV occurs at or during afourth time interval T4, and/or that the second transmission of thesecond TB with the second RV occurs at or during a fifth time intervalT5. The second DCI may indicate a second HARQ process (e.g., HARQprocess y) associated with the second TB. The second DCI may indicate asecond HARQ-ACK feedback timing value for the second TB. The secondHARQ-ACK feedback timing value may indicate that the wireless device isrequired to send/transmit the second HARQ-ACK information at or during aquantity/number of time intervals after the wireless device processesthe second TB (e.g., the first transmission of the second TB, and/or thesecond transmission of the second TB). The second time interval T2 mayoccur a quantity/number of time intervals after the first time intervalT1. The fourth time interval T4 may occur a quantity/number of timeintervals after the third time interval T3. The second TB may arrivebefore the first TB, for example, if an out-of-scheduling is supported(e.g., the second TB may arrive at or during the third time interval T3and the first TB may arrive at or during the fourth time interval T4.The wireless device may, based on the first DCI and the second DCI,determine that a second HARQ-ACK feedback for the first transmission ofthe second TB is out-of-order, compared with the first HARQ-ACK feedbackfor the first TB. The wireless device may determine that the secondHARQ-ACK feedback for the first transmission of the second TB isout-of-order, for example, based on the reception orders of the firstDCI and the second DCI. The wireless device may determine that thesecond HARQ-ACK feedback for the first transmission of the second TB isout-of-order, for example, based on the second HARQ-ACK feedback beingscheduled to be sent/transmitted before sending/transmitting the firstHARQ-ACK feedback. The wireless device may, based on the first TB andthe second TB, determine that the second HARQ-ACK feedback for the firsttransmission of the second TB is out-of-order, compared with the firstHARQ-ACK feedback for the first TB. The wireless device may determinethat the second HARQ-ACK feedback for the first transmission of thesecond TB is out-of-order, for example, based on the reception orders ofthe first TB and the second TB and/or based on the second HARQ-ACKfeedback being scheduled to be sent/transmitted beforesending/transmitting the first HARQ-ACK feedback. The first TB may bereferred to as a low-priority TB. The second TB may be referred to as ahigh-priority TB.

The wireless device may determine to not generate (e.g., refrain fromgenerating) HARQ-ACK information for the second TB, for example, basedon determining that the second HARQ-ACK feedback for a first repetitionof a second TB is out-of-order, and/or if there is a lower-priority TBpending for processing. The wireless device may generate the secondHARQ-ACK information for the second TB, for example, after receiving asecond repetition of the second TB (e.g., at or during the fifth timeinterval T5). The wireless device may process the first TB, for example,based on determining to not generate (e.g., refrain from generating)HARQ-ACK information for the second TB. The wireless device maysend/transmit HARQ-ACK information for the first TB and/or the second TB(e.g., at or during a sixth time interval T6), for example, based on theprocessing the first TB and the second TB. Various configurationsdescribed herein may improve system throughput and/or data transmissionlatency, or reduce power consumption of the wireless device and/orimplementation cost.

A base station may send/transmit, to a wireless device, DCI comprising apriority field indicating a prioritized PDSCH transmission. The basestation may send/transmit the DCI comprising a priority field, forexample, in at least some types of communications (e.g., communicationsby wireless devices compatible with 3GPP Release 15, earlier/later 3GPPreleases, and/or any other access technologies). The wireless device maydetermine that processing of a first TB is prioritized over processingof a second TB, for example, based on a first priority value of apriority field in first DCI (e.g., scheduling the first TB) and a secondpriority value of a priority field in second DCI (e.g., scheduling thesecond TB). The wireless device may determine that processing of thefirst TB is prioritized over processing of the second TB, for example,based on the first priority value being higher than the second priorityvalue (e.g., a higher priority value indicates a higher priority). Thewireless device may determine that processing of the first TB isprioritized over processing of the second TB, for example, based on thefirst priority value being lower than the second priority value (e.g., alower priority value indicates a higher priority). The first DCI and/orthe second DCI, different from DCI formats (e.g., DCI format 0_0/0_1,and/or DCI format 1_0/1_1), may comprise the priority field indicating aPDSCH transmission priority or PUSCH transmission priority. The DCIformats may not comprise the priority field indicating the PDSCHtransmission priority or the PUSCH transmission priority.

In some types of wireless communications (e.g., compatible with 3GPPRelease 16, earlier/later 3GPP releases or generations, and/or otheraccess technology), a wireless device may receive one or more DCImessages that do not comprise a priority field associated with aprioritized PDSCH transmission. A wireless device may determine (or berequired) to send/transmit a signal and/or process a signal withouthaving sufficient information to determine an appropriate priority forone or more signal transmissions and/or signal processing. A wirelessdevice may not be able to compare priority values of different channels,data, and/or transmissions, for example, if a priority value for atleast one channel, data, and/or transmission is absent and the differentchannels, data, and/or transmissions overlap with each other and/orshare the same resource. The wireless device may receive first DCIcomprising a priority field, for example, before receiving second DCInot comprising a priority field (or the wireless device may receivefirst DCI not comprising a priority field, for example, before receivingsecond DCI comprising a priority field). The first DCI may indicate ascheduled transmission of a first TB. The second DCI may indicate ascheduled transmission of a second TB. The scheduled transmission of thefirst TB may occur before the scheduled transmission of the second TB. Asecond HARQ-ACK feedback for the second TB may be required to besent/transmitted before sending/transmitting a first HARQ-ACK feedbackfor the first TB. A wireless device may have difficulties in determiningwhether to drop processing of a TB, for example, if TBs are scheduled byDCI messages comprising DCI with a priority field and DCI without apriority field, and two HARQ-ACK feedbacks for the TBs are out-of-order.A wireless device may not be able to compare priority values associatedwith the two DCI messages (e.g., associated with different DCIconfigurations). As described further herein, improved out-of-orderprocessing may be used/configured, for example, if multiple differentDCI formats and out-of-order processing are supported.

As described herein, enhanced data processing may use/compriseprocessing based on priority. Data processing may be performed based onwhether control information comprises a priority field. If controlinformation does not comprise, or lacks, a priority field, at least oneparameter may be used to determine a priority associated with thecontrol information. A wireless device may determine a priority valueassociated with a second channel, second data, and/or a secondtransmission, for example, if the wireless device determines that apriority value associated with a first channel, first data, and/or afirst transmission exists and that a priority value associated with thesecond channel, the second data, and/or the second transmission does notexist. The wireless device may determine the priority value associatedwith the second channel, the second data, and/or the secondtransmission, for example, based on a default value (e.g., zero or anyother value) and/or a value determined based on a preset rule. Thewireless device may compare the determined priority value associatedwith the second channel, the second data, and/or the second transmissionwith the priority value associated with the first channel, first data,and/or the first transmission, for example, to perform data processing.Determination and use of a priority value for one or more channels,data, and/or transmissions as described herein may provide advantagessuch as reduced misalignment, improved resource allocations, improvedflexible data scheduling, reduced signaling overhead/retransmissions,reduced interference, reduced wireless device and/or base stationbattery/power consumption, and/or reduced delay/latency ofcommunication.

FIG. 30A shows an example of out-of-order processing. A wireless devicemay receive, from a base station, first DCI (e.g., at or during a firsttime interval T1). The base station may send/transmit the first DCI,corresponding to a first DCI format (e.g., DCI format 1_2, differentfrom DCI format 1_0/1_1), comprising a priority field (e.g., 1, 2, orany quantity/number of bits greater than 0) with a first priority valueindicating a first PDSCH transmission priority for a first TB. Apriority value of the priority field of the first DCI format mayindicate a priority level of PDSCH transmission of a TB. The first DCImay indicate that the first TB is scheduled to be sent/transmitted(e.g., at or during a third time interval T3). The first DCI maycomprise a first HARQ-ACK feedback timing value that indicates a firstHARQ-ACK feedback is required to be sent/transmitted (e.g., at or duringa sixth time interval T6). The base station may have available and/orurgent data (e.g., a second TB) to be sent/transmitted to the wirelessdevice. The base station may determine to send/transmit second DCIcorresponding to a second DCI format (at or during a second timeinterval T2), for example, after sending/transmitting the first DCIcorresponding the first DCI format. The second DCI may indicate that thesecond TB is scheduled to be sent/transmitted (e.g., at or during athird time interval T3). The second DCI format, different from the firstDCI format, may not comprise a priority field. The second DCI format maycomprise a DCI format (e.g., a 3GPP DCI format, such as DCI format1_0/1_1). The second DCI may be sent/transmitted via a search space or acontrol resource set configured with a DCI format (e.g., DCI format1_0/1_1) and configured without a new DCI format (e.g., DCI format 1_2with a priority field). The second DCI may indicate that the second TBis scheduled to be sent/transmitted (e.g., at or during a fourth timeinterval T4). The second DCI may comprise a second HARQ-ACK feedbacktiming value indicating that a second HARQ-ACK feedback is required tobe sent/transmitted (e.g., at or during a fifth time interval T5). Thewireless device may determine that the second HARQ-ACK feedback for thesecond TB is an out-of-order HARQ feedback compared with the firstHARQ-ACK feedback for the first TB, for example, based on the firstHARQ-ACK feedback timing value and the second HARQ-ACK feedback timingvalue.

A wireless device may determine that the second TB is prioritized overthe first TB. The wireless device may determine that the second TB isprioritized over the first TB, for example, based on (e.g., after or inresponse to) the determining that the second HARQ-ACK feedback for thesecond TB is out-of-order. The wireless device may determine that thesecond TB is prioritized over the first TB, for example, if the firstDCI indicates a PDSCH transmission priority for the first TB and thesecond DCI does not indicate a PDSCH transmission priority for thesecond TB. The wireless device may determine to drop processing of thefirst TB (e.g., at or during a third time interval T3), for example,based on (e.g., after or in response to) the determining that the secondHARQ-ACK feedback for the second TB is out-of-order. The wireless devicemay determine to drop processing of the first TB (e.g., at or during thethird time interval T3), for example, if the first DCI indicates a PDSCHtransmission priority for the first TB and the second DCI does notindicate a PDSCH transmission priority for the second TB. The wirelessdevice may process the second TB (e.g., at or during a fourth timeinterval T4) and send/transmit the second HARQ-ACK information for thesecond TB (e.g., at or during a fifth time interval T5), for example,based on (e.g., after or in response to) dropping the processing of thefirst TB. The wireless device may send/transmit the first HARQ-ACKinformation for the first TB (e.g., at or during a sixth time intervalT6), for example, based on (e.g., after or in response to) dropping theprocessing of the first TB. The first HARQ-ACK information may comprisea negative acknowledgment for the first TB. A wireless device mayprioritize processing of a second TB scheduled by DCI corresponding to afirst DCI format (e.g., DCI format 1_0/1_1 without a priority field)over processing of a first TB scheduled by DCI corresponding to a secondDCI format (e.g., DCI format 1_2 with a priority field, or a new DCIformat in 3GPP future releases or any other communications), forexample, if a second HARQ-ACK information feedback for the second TB isout-of-order compared with a first HARQ-ACK information feedback for thefirst TB. A wireless device may prioritize processing of a second TBscheduled by DCI corresponding to a first DCI format (e.g., DCI format1_0/1_1 without a priority field) over processing of a first TBscheduled by DCI corresponding to a second DCI format (e.g., DCI format1_2 with a priority field, or a new DCI format in 3GPP future releasesor any other communications), for example, if the transmission of thesecond TB is out-of-order before the transmission of the first TB. Byspecifying/applying TB processing dropping rules, advantages may beachieved such as reduced between a base station and a wireless device(e.g., regarding determining whether dropping processing of a TB occurs,for example, if mixed DCI formats are supported in the system), reduceddata transmission latency, and/or increased system throughput.

The wireless device may determine a default priority value for thesecond TB. The wireless device may determine a default priority valuefor the second TB, for example, if the wireless device receives firstDCI configured with a priority field for a first TB, and second DCIconfigured without a priority field for a second TB. The wireless devicemay determine the default priority value for the second TB, for example,based on the second DCI not being configured with a priority field. Thepriority field of the first DCI may indicate a PDSCH transmissionpriority value (e.g., 0, 1, 2, 3 or any number greater than 0). Thedefault priority value may be predefined to a fixed value (e.g., 0). Thewireless device may determine whether the first TB has higher priority,or the second TB has higher priority, for example, based on comparingthe default priority value of the second TB and a priority valueindicated by the priority field of the first DCI for the first TB.

FIG. 30B shows an example of out-of-order processing. The base stationand/or the wireless device may perform one or more operations similar tothose described above with respect to FIG. 30A, except that the defaultpriority value may indicate a lower priority. The base station maysend/transmit, to the wireless device, first DCI corresponding to afirst DCI format comprising a priority field (e.g., at or during a firsttime interval T1). The base station may send/transmit, to the wirelessdevice, second DCI corresponding to a second DCI format not comprising apriority field (e.g., at or during a second time interval T2). The firstDCI may schedule a transmission of a first TB (e.g., at or during athird time interval T3). The second DCI may schedule a transmission of asecond TB (e.g., at or during a fourth time interval T4). The basestation may send/transmit, to the wireless device, the first TB (e.g.,at or during the third time interval T3). The base station maysend/transmit, to the wireless device, the second TB (e.g., at or duringthe fourth time interval T4). The wireless device may prioritizeprocessing of the first TB, for example, if the wireless device receivesthe first DCI configured with a priority field for the first TB and thesecond DCI configured without a priority field for the second TB. Thefirst DCI may be sent/transmitted before sending/transmitting the secondDCI. The first DCI may be sent/transmitted after sending/transmittingthe second DCI The wireless device may prioritize processing of thefirst TB (e.g., by dropping processing of the second TB), for example,if a base station send/transmits the second TB beforesending/transmitting the first TB. The wireless device may process thefirst TB (e.g., via HARQ process x), for example, after receiving thefirst TB via the first PDSCH and based on the determined priorities. Thewireless device may drop processing of the second TB (e.g., droppingHARQ process y), for example, based on the determined priorities. Thewireless device may prioritize processing of the first TB (e.g., bydropping processing of the second TB), for example, if a base stationsends/transmits the second TB after sending/transmitting the first TB.The wireless device may prioritize processing of the first TB (e.g., bydropping processing the second TB), for example, if a second HARQ-ACKinformation feedback for the second TB is out-of-order compared with afirst HARQ-ACK information feedback for the first TB. The wirelessdevice may send/transmit the first HARQ-ACK information feedback for thefirst TB and may drop the second HARQ-ACK information feedback for thesecond TB (e.g., at or during a fifth time period T5), for example,based on the first DCI comprising the priority field and for the firstTB and the second DCI not comprising a priority field for the second TBand/or based on a first uplink resource (e.g., PUCCH or PUSCHresource(s)) for sending/transmitting the first HARQ-ACK informationfeedback for the first TB overlapping (e.g., at least partially) with asecond uplink resource (e.g., PUCCH or PUSCH resource(s)) forsending/transmitting the second HARQ-ACK information feedback for thesecond TB. The improved priority processing described herein may reducemisalignment between a base station and a wireless device (e.g., fordetermining whether processing of a TB is dropped) and/or may improvedata transmission latency and/or system throughput.

Processing of a higher priority TB may be dropped, for example, if anHARQ-ACK feedback is out-of-order. The second DCI format may be the same(or substantially the same) as the first DCI format. The second DCIformat may comprise a priority field with a second priority valueindicating a second PDSCH transmission priority for a second TB. Thefirst TB may have higher priority than the second TB, for example, basedon comparing the first priority value of the first DCI and the secondpriority value of the second DCI. The wireless device may determine thatthe second HARQ-ACK feedback for the second TB is out-of-order comparedwith the first HARQ-ACK feedback for the first TB, while the first TBhas higher priority than the second TB. The wireless device maydetermine to drop processing of the first TB, for example, based on thesecond HARQ-ACK feedback being out-of-order, if the first TB has higherpriority of transmission than the second TB. The wireless device mayignore the priority and may follow the HARQ-ACK processing order (e.g.,dropping the first TB and processing the second TB with out-of-orderHARQ-ACK feedback), for example, if an HARQ-ACK feedback isout-of-order.

Referring back to FIG. 30A, the wireless device may process the secondTB (e.g., at or during a fourth time interval T4) and/or send/transmitthe second HARQ-ACK information (e.g., at or during a fifth timeinterval T5), for example, based on (e.g., after or in response to)dropping the processing of the first TB. The wireless device maysend/transmit the first HARQ-ACK information (e.g., at or during a sixthtime interval T6). The improved out-of-order processing described hereinmay reduce misalignment between a base station and a wireless device(e.g., for determining whether processing of a TB is dropped) and/or mayimprove data transmission latency and/or system throughput.

The second DCI format may be the same (or substantially the same) as thefirst DCI format. Both the first DCI format and the second DCI formatmay comprise a priority field. The second DCI format may comprise apriority field with a second priority value indicating a second PDSCHtransmission priority for a second TB. The first TB may have higherpriority than the second TB, for example, based on comparing the firstpriority value of the first DCI and the second priority value of thesecond DCI. The wireless device may determine that the second HARQ-ACKfeedback for the second TB is out-of-order compared with the firstHARQ-ACK feedback for the first TB, while the first TB has higherpriority than the second TB. The wireless device may determine to dropprocessing of the second TB, for example, based on the first TB havinghigher priority of transmission than the second TB and the secondHARQ-ACK feedback for the second TB being out-of-order. The wirelessdevice may process the first TB, and/or send/transmit the first HARQ-ACKinformation for the first TB, for example, based on (e.g., after or inresponse to) dropping processing of the second TB. The improvedout-of-order processing described herein may reduce misalignment betweena base station and a wireless device (e.g., for determining whetherprocessing of a TB is dropped) and/or may improve data transmissionlatency and/or system throughput.

A wireless device may receive configuration parameters indicating a datapreparation time parameter. A wireless device may receive from a basestation one or more RRC messages comprising configuration parametersindicating a PUSCH preparation time threshold (N2). N2 may be 10 (ifu=0), 12 (if u=1), 23 (if u=2), or 36 (if u=3), or any other value(e.g., if u=n, where n may be any particular value), for example, ifPUSCH timing capability 1 is supported by the wireless device. u is anumerology index (e.g., 0, 1, 2, or 3) indicating a numerology used inPUSCH (or PDCCH for the DCI transmission). N2 may be 5 (if u=0), 5.5 (ifu=1), or 11 (if u=2 and for frequency range 1), or any other value(e.g., if u=n, where n may be any particular value), for example, ifPUSCH timing capability 2 is supported by the wireless device. The oneor more RRC messages may comprise at least one of: ServingCellConfig IE;CellGroupConfig IE; an RRCSetup message; and/or an RRCReconfigurationmessage. The wireless device may determine whether to send/transmit aPUSCH at a second time interval after receiving DCI at a first timeinterval, for example, based on the PUSCH preparation time threshold.The wireless device may determine to send/transmit the PUSCH, forexample, based on a time duration between the first time interval andthe second time interval being equal to or greater than a PUSCHprocessing time (e.g., Tproc, 2). The PUSCH processing time may bedetermined as Tproc, 2=max((N2+d2,1)(2048+144)*k*2{circumflex over( )}(−u)*Tc, d2,2), where k=64, Tc=1/(Δfmax*Nf), Δfmax=480*10{circumflexover ( )}3 Hz and Nf=4096. d2,1=0, for example, if the first symbol ofthe PUSCH allocation consists of DM-RS only, otherwise d2,1=1. d2,2 mayequal to a BWP switching time, for example, if the DCI triggers a BWPswitching, otherwise d2,2=0. The wireless device may ignore the DCI(e.g., by not sending/transmitting the PUSCH), for example, based on thetime duration between the first time interval and the second timeinterval being less than the PUSCH processing time.

A wireless device may perform uplink transmission(s), for example, basedon an out-of-order grant. A wireless device may send/transmit a secondTB via the out-of-order grant, and drop transmission of a first TB, forexample, based on (e.g., after or in response to) receiving anout-of-order grant for the second TB after receiving a first grant forthe first TB. Dropping transmission of a low-priority TB may improvepower consumption, reduce implementation cost, or improve datatransmission latency for a high-priority TB. Consistent dropping of thetransmission of the first TB may reduce uplink system throughput, orincrease uplink transmission latency.

FIG. 31 shows an example of out-of-order grant processing. A wirelessdevice may receive (e.g., at or during a first time interval T1), from abase station, at least a portion of first DCI indicating a first uplinkTB transmission via a first PUSCH (e.g., at or during a fourth timeinterval T4). The wireless device may receive (e.g., at or during asecond time interval T2) second DCI indicating a second uplink TBtransmission via a second PUSCH (e.g., at or during a third timeinterval T3). The first time interval T1 may occur before the secondtime interval T2. The third time interval T3 may occur before the fourthtime interval T4. The first uplink TB may be associated with a firstHARQ process (e.g., HARQ process y). The second uplink TB may beassociated with a second HARQ process (e.g., HARQ process x). Thewireless device may receive at least a portion of the first DCI beforereceiving at least a portion of the second DCI. The wireless device maybe required to send/transmit at least a portion of the second TB (e.g.,an initial portion or all of the second TB) via the second PUSCH beforesending/transmitting at least a portion of the first TB (e.g., aninitial portion or all of the first TB) via the first PUSCH.Sending/transmitting the second TB before sending/transmitting the firstTB, and receiving the first DCI before receiving the second DCI, may bereferred to as an out-of-order grant.

The wireless device may determine a time gap between a first timeoccasion of the first PUSCH and a second time occasion of the secondPUSCH, for example, based on (e.g., after or in response to) receivingan out-of-order grant for the second TB via the second PUSCH. The firsttime occasion of the first PUSCH may comprise at least one of: the firstuplink symbol of the first PUSCH in time domain, or the last uplinksymbol of the first PUSCH in time domain. The second time occasion ofthe second PUSCH may be the first uplink symbol of the second PUSCH intime domain. The wireless device may send/transmit at least a portion ofthe second TB (e.g., at or during a third time interval T3), forexample, based on (e.g., after or in response to) receiving anout-of-order grant for transmission of the second TB via the secondPUSCH. The wireless device may determine whether to send/transmit thefirst PUSCH, for example, based on the time gap and the PUSCH processingtime. The wireless device may determine to send/transmit the first TBvia the first PUSCH, for example, based on the time gap being equal toor greater than the PUSCH processing time. The wireless device maydetermine to ignore the first DCI (e.g., by not sending/transmitting thefirst TB via the first PUSCH), for example, based on the time gap beingless than the PUSCH processing time. The wireless device may determinewhether to send/transmit a low-priority TB via a PUSCH, for example,based on a first time gap between two PUSCH transmission occasions(e.g., one being scheduled on an out-of-order grant), rather than basedon a second time gap between a DCI reception and a PUSCH transmissionoccasion. The wireless device may determine whether to send/transmit alow-priority TB via a PUSCH, rather than always drop transmission of thelow-priority TB, for example, based on a first time gap between twoPUSCH transmission occasions (e.g., one being scheduled on anout-of-order grant). The wireless device may determine whether tosend/transmit a low-priority TB via a PUSCH, for example, based on thefirst DCI being sent/transmitted from a first TRP (e.g., of the basestation) and the second DCI being sent/transmitted from a second TRP(e.g., of the base station) and/or based on the first TB beingsent/transmitted to the first TRP and the second TB beingsent/transmitted to the second TRP. The wireless device may determinewhether to send/transmit a low-priority TB via a PUSCH, for example,based on the first DCI being sent/transmitted to a first antenna panelof the wireless device and the second DCI being sent/transmitted to asecond antenna panel of the wireless device and/or based on the first TBbeing sent/transmitted from the first antenna panel of the wirelessdevice and the second TB being sent/transmitted from the second antennapanel of the wireless device. The improved out-of-order grant processingdescribed herein may enable alignment between the base station and thewireless device (e.g., for determining whether a low-priority TB issent/transmitted or not) and/or may improve data transmission latency,and/or reduce device complexity.

A wireless device may send/transmit a second TB, for example, based on(e.g., after or in response to) receiving an out-of-order grant fortransmission of the second TB via a second PUSCH. The wireless devicemay determine to delay a transmission of a first TB via a first PUSCH,for example, based on (e.g., after or in response to) transmitting thesecond TB, so that a time gap between a first time of a transmission ofthe second TB and a second time of a delayed transmission of the firstTB is equal to or greater than the PUSCH processing time. The improvedout-of-order grant processing described herein may enable alignmentbetween the base station and the wireless device (e.g., for determiningwhether a low-priority TB is sent/transmitted or not) and/or may improvedata transmission latency, and/or reduce device complexity.

FIG. 32A shows example communications for multiple TRPs and/or multipleantenna panels. A base station may be equipped with more than one TRP(e.g., TRP 1 and TRP 2 shown in FIG. 32A). A wireless device may beequipped with more than one panel (e.g., Panel 1 and Panel 2 shown inFIG. 32A). Transmission and reception using multiple TRPs and multipleantenna panels may improve system throughput and/or transmissionrobustness for a wireless communication in a high frequency (e.g., above6 GHz). The TRP 1 of the base station may send/transmit first DCIscheduling a first TB. The Panel 1 of the wireless device may receivethe first DCI. The first TB may be sent/transmitted via a first PDSCH.The TRP 2 of the base station may send/transmit second DCI scheduling asecond TB. The Panel 2 of the wireless device may receive the secondDCI. The second TB may be sent/transmitted via a second PDSCH. The TRP 1of the base station may receive, from the Panel 1 of the wirelessdevice, first HARQ feedback associated with the first TB. The first HARQfeedback may be sent/transmitted via a first PUSCH. The TRP 2 of thebase station may receive, from the Panel 2 of the wireless device,second HARQ feedback associated with the second TB. The second HARQfeedback may be sent/transmitted via a second PUSCH. While some figuresand/or descriptions herein provide one or more configurations formultiple TRPs, data processing (e.g., out-of-order processing) formultiple TRPs may be applicable to multiple antenna panels in the sameor similar way. For example, a first antenna panel (e.g., Panel 1 inFIG. 32A) of a wireless device may receive first DCI and a first TB andsend/transmit first HARQ-ACK feedback, and a second antenna panel (e.g.,Panel 2 in FIG. 32A) of the wireless device may receive second DCI and asecond TB and send/transmit second HARQ-ACK feedback.

FIG. 32B shows an example of transmission and reception via multipleTRPs and/or multiple antenna panels. Two PDSCH transmissions may beperformed via two TRPs. Any quantity of PDSCH transmissions may beperformed via any quantity of TRPs. The base station may send/transmit,to the wireless device, first DCI scheduling a first TB via a firstPDSCH of the first TRP (e.g., using a first panel), for example, if themultiple TRPs and/or the multiple antenna panels are configured. Thebase station may send/transmit, to the wireless device, second DCIscheduling a second TB via a second PDSCH of the second TRP (e.g., usinga second panel), for example, if the multiple TRPs and/or the multipleantenna panels are configured. The base station may be allowed tosend/transmit the first downlink TB via the first TRP and the seconddownlink TB via the second TRP with a shared time and/or frequencyresource (e.g., and/or with different transmission beams), for example,unlike a single TRP and/or single panel configuration. In comparisonwith the single TRP/panel configuration, the base station may improvesystem throughput or transmission robustness if multiple TRPs and/ormultiple antenna panels are configured.

In some types of wireless communications (e.g., compatible with 3GPPRelease 16, earlier/later 3GPP releases or generations, and/or otheraccess technology), a wireless device may drop and/or not process achannel, data, and/or a transmission. The wireless device may dropprocessing due to various reasons, such as a plurality of channels,data, and/or transmissions overlap with each other in one or moreresources; out-of-order processing occurs; insufficient wireless devicecapability, and/or any other reason for which processing may not occur.Dropping processing of low-priority channels, data, and/or transmissionsas a default rule may be inefficient.

As described further herein, out-of-order processing may be improvedusing different resource groups (e.g., multiple TRPs, multiple antennapanels, and/or multiple other resources). Communications and/or dataprocessing may be performed (e.g., in-order, out-of-order, and/oroverlapping), based on one or more configurations of resource groups. Awireless device may determine whether to process data, for example,based on whether a plurality of channels are associated with differentresource groups. The wireless device may process a plurality ofchannels, data, and/or transmissions, for example, for out-of-orderprocess based on whether a first resource and a second resource being in(e.g., belonging to) different resource groups (e.g., multiple CORESETS,multiple TRPs, multiple antenna panels, etc.). As described herein, byusing improved out-of-order processing and multiple resources (e.g.,multiple CORESETS, multiple TRPs and/or multiple antenna panels), a basestation and/or a wireless device may improve data transmission latencyand/or system throughput (e.g., if multiple TRPs and/or multiple antennapanels, and out-of-order processing, are supported).

In some types of wireless communications (e.g., compatible with 3GPPRelease 16, earlier/later 3GPP releases or generations, and/or otheraccess technology), a wireless device may drop and/or not processing achannel, data, and/or a transmission. The wireless device may dropprocessing due to various reasons, such as a plurality of channels,data, and/or transmissions overlap with each other in one or moreresources; out-of-order processing occurs; insufficient wireless devicecapability; and/or any other reason for which processing may not occur.Dropping processing of low-priority channels, data, and/or transmissionsas a default rule may be inefficient for at least some types of wirelesscommunications. Yet, at least some types of wireless communications mayrequire a wireless device to drop processing of a low-priority TB, forexample, if the wireless device receives an out-of-order scheduling,and/or if the wireless device processes an out-of-order HARQ-ACKfeedback. At least some types of wireless communications may allow awireless device to determine whether to the processing of thelow-priority TB, for example, if the wireless device receives theout-of-order scheduling and/or processes the out-of-order HARQ-ACKfeedback, based on one or more capability parameters of the wirelessdevice (e.g., the maximum number of carriers aggregated; the maximumnumber of MIMO layers or antenna ports). A base station maysend/transmit a TB via a first TRP or a second TRP, for example, ifmultiple TRPs are supported. The base station may send/transmit a TB viaboth a first TRP and a second TRP, for example, if multiple TRPs aresupported. In some types of wireless communications, a wireless devicemay have difficulties in determining dropping conditions, for example,if the wireless device receives multiple DCI messages from differentTRPs (e.g., scheduling multiple PDSCHs to be sent/transmitted via thedifferent TRPs). The wireless device may have difficulties indetermining whether to drop processing of a first TB received via afirst TRP (or via the first TRP and via the second TRP), for example, ifthe wireless performs out-of-order processing for a second TB receivedvia a second TRP (or via the first TRP and via the second TRP), and/orif the first TB is a low-priority TB and the second TB is ahigh-priority TB. Reduction of system throughputs and/or increased datatransmission latency may result, for example, if a wireless deviceexperiences difficulties in determining whether to drop processing.

As described further herein, data processing may be improved using aplurality of resource groups (e.g., multiple TRPs, multiple antennapanels, and/or multiple other resources). A plurality of resources maybe indicated for a wireless device to use to process data. At least somedata may be indicated to be processed in-order, out-of-order, and/oroverlapping with other data. Data may be processed or not processed,based on whether the plurality of resources to be used are associatedwith different resource groups. For example, a wireless device may becapable of processing out-of-order and/or overlapping data transmissionsif the wireless device is configured to use different resource groups,whereas a wireless device may not be capable of processing out-of-orderand/or overlapping data transmissions if the wireless device is notconfigured to use different resource groups. Communications and/or dataprocessing may be performed (e.g., in-order, out-of-order, and/oroverlapped) based on one or more configurations of resource groups. Awireless device may determine whether to process data, for example,based on whether a plurality of channels are associated with differentresource groups. A wireless device may determine one or more firstchannels, first data, and/or first transmissions that are processed(e.g., together or in succession) without dropping, and may determineone or more second channels, second data, and/or second transmissionsthat are dropped from processing, for example, based on one or morerules, factors, and/or conditions in one or more configurations (e.g.,associated with multiple TRPs, multiple antenna panels, and/or multipleresource groups). Dropping data processing may be determined, forexample, based on whether channels, data, and/or transmissions areassociated with the same or different TRPs, the same or differentantenna panels, and/or the same or different resource groups (e.g.,CORESETS) Channels, data, and/or transmission may be scheduled via thesame or different TRPs, the same or different antenna panels, and/or thesame or different resource groups, for example, based on whether or notone or more types of channels, data, and/or transmissions are allowed tobe dropped. Determination of co-processing, or partial dropping of dataprocessing, for one or more channels, data, and/or transmissions asdescribed further herein may provide advantages such as reducedmisalignment, improved resource allocations, improve flexible datascheduling, reduced signaling overhead/retransmissions, reducedinterference, reduced wireless device and/or base station battery/powerconsumption, and/or reduced delay/latency of communication.

FIG. 33, FIG. 34A, and FIG. 34B show examples of out-of-order processingfor multiple TRPs and/or multiple antenna panels. A base station maysend/transmit, from a first TRP (e.g., TRP 1) to a wireless device, atleast a portion of first DCI (e.g., at or during a first time intervalT1) indicating a transmission of a first TB via a first PDSCH resource(e.g., at or during a third time interval T3, for example, as shown inFIG. 34A, or at or during a third time interval T4, for example, asshown in FIGS. 26B, 33 and 34B). The first DCI may indicate that a firstHARQ-ACK feedback is to be sent/transmitted (e.g., at or during a sixthtime interval T6, for example, as shown in FIG. 34A). The wirelessdevice may determine an out-of-order scheduling of the transmission ofthe second TB (e.g., in comparison with the transmission of the firstTB) (e.g., as shown in FIGS. 26B and 33). The wireless device maydetermine to process the second TB, and may determine to whether toprocess the first TB, for example, based on whether or not the first DCIand the second DCI being received from/via the same TRP. The wirelessdevice may process the first TB, for example, based on determining thatthat second DCI is received from/via a TRP different from a TRP from/viawhich the first DCI is received. The wireless device may determine toprocess both the first TB and the second TB, for example, based ondetermining that the first DCI and the second DCI are received viadifferent CORESET groups. The wireless device may process the first TBand the second TB, for example, based on determining that the first DCIis received via a CORESET of a first CORESET group and the second DCI isreceived via a CORESET of a second CORESET group different from thefirst CORESET group.

The base station may send/transmit at least a portion of the first TBvia the first PDSCH resource (e.g., at or during a third time intervalT3, for example, as shown in FIG. 34A, or at or during a third timeinterval T4, for example, as shown in FIG. 34B). The base station maysend/transmit, from a second TRP (e.g., TRP 2) to the wireless device,at least a portion of second DCI (e.g., at or during a second timeinterval T2) indicating a transmission of a second TB via a second PDSCHresource (e.g., at or during a fourth time interval T4, for example, asshown in FIG. 34A, or at or during a third time interval T3, forexample, as shown in FIGS. 26B, 33 and 34B). The second DCI may indicatethat a second HARQ-ACK feedback is to be sent/transmitted (e.g., at orduring a fifth time interval T5, for example, as shown in FIG. 34A). Thebase station may send/transmit at least a portion of the second TB viathe second PDSCH resource (e.g., at or during a fourth time interval T4,for example, as shown in FIG. 34A, or at or during a third time intervalT3, for example, as shown in FIG. 34B). One or more of the first DCI,the second DCI, the first TB, or the second TB may at least partiallyoverlap in time with the other one of the first DCI, the second DCI, thefirst TB, or the second TB (e.g., the second DCI at least partiallyoverlaps in time with the first TB as shown in FIG. 34A). The first TBmay be associated with a first HARQ process (e.g., HARQ process x, forexample, as shown in FIG. 34A). The second TB may be associated with asecond HARQ process (e.g., HARQ process y, for example, as shown in FIG.34A). The second HARQ-ACK feedback may be out-of-order, for example,based on the second HARQ-ACK information being feedbacked before thefirst HARQ-ACK information, while the second TB is sent/transmittedafter sending/transmitting the first TB. A TRP of multiple TRPs of thebase station may be determined/identified by, or associated with, atleast one of: a TRP identifier (ID), a cell index, or a reference signalindex. A TRP ID of a TRP may comprise a CORESET group index of a CORESETgroup comprising a CORESET via which DCI is sent/transmitted from thebase station. A TRP ID of a TRP may comprise a TRP index indicated inthe DCI. A TRP ID of a TRP may comprise a TCI state group index of a TCIstate group. A TCI state group may comprise at least one TCI state withwhich the wireless device receives the downlink TBs, and/or with whichthe base station sends/transmits the downlink TBs.

The wireless device may process a plurality of TBs (e.g., inout-of-order processing), for example, if multiple TRPs and/or antennapanels are configured. As shown in FIG. 34A, the wireless device maydetermine to process both the first TB and the second TB, for example,based on the second HARQ-ACK being out-of-order, and/or if the first TBis scheduled to be sent/transmitted via the first TRP and the second TBis scheduled to be sent/transmitted via the second TRP. The wirelessdevice may receive and/or process the first TB associated with the firstHARQ process via the first TRP (e.g., at or during the third timeinterval T3), for example based on the determining to process both thefirst TB and the second TB. The wireless device may receive and/orprocess the second TB associated with the second HARQ process via thesecond TRP (e.g., at or during the fourth time interval T4), forexample, based on the determining to process both the first TB and thesecond TB. The wireless device may send/transmit the second HARQ-ACKinformation for the second TB (e.g., at or during the fifth timeinterval T5) and send/transmit the first HARQ-ACK information for thefirst TB (e.g., at or during the sixth time interval T6), for example,based on the processing of the first TB and the second TB. The wirelessdevice may send/transmit the first HARQ-ACK information for the first TB(e.g., at or during the fifth time interval T5) and send/transmit thesecond HARQ-ACK information for the second TB (e.g., at or during thesixth time interval T6), for example, based on the processing of thefirst TB and the second TB). The wireless device may process both thelow-priority TB and a high-priority TB (e.g., without dropping thelow-priority TB), for example, if the wireless device performsout-of-order processing, based on the low-priority TB and thehigh-priority TB being sent/transmitted from different TRPs of a basestation (e.g., unlike a single TRP case where a wireless device mayprocess a high-priority TB and drop processing of a low-priority TBwhile performing out-of-order processing). A wireless device may processa high-priority TB and drop a low-priority TB, for example, if thewireless device performs out-of-order processing, based on thelow-priority TB and the high-priority TB being sent/transmitted from thesame TRP of a base station (or via the same CORESET group). A wirelessdevice may determine whether to drop the low-priority TB forout-of-order processing, for example, based on whether a low-priority TBand a high-priority TB are sent/transmitted from a same TRP or fromdifferent TRPs. As described herein, by using multiple TRPs and/ormultiple antenna panels, a base station and/or a wireless device mayimprove data transmission latency and/or system throughput (e.g., ifmultiple TRPs and/or multiple antenna panels and out-of-order processingare supported).

FIG. 35A shows an example of out-of-order processing for multiple TRPsand/or multiple antenna panels. Out-of-order processing may be based onmultiple TRPs and/or multiple antenna panels (e.g., if multiple TRPsand/or multiple antenna panels are supported). A base station maysend/transmit, from a first TRP (e.g., TRP 1) to a wireless device,first DCI (e.g., at or during a first time interval T1), indicatingtransmissions (or repetitions) of a first TB via the first TRP and via asecond TRP (e.g., TRP 2). The transmissions of the first TB via thefirst TRP and via the second TRP may comprise a transmission of thefirst TB using a first RV value via the first TRP (e.g., at or during athird time interval T3) and a repetition of the first TB using a secondRV value via the second TRP (e.g., at or during a time interval T3′,which may be in proximity to the third time interval T3). The first RVvalue may be the same as or different from the second RV value, and/orthe third time interval T3 may be same as or different from the timeinterval T3′. The transmissions of the first TB via the first TRP andvia the second TRP may comprise a first transmission of first layers ofthe first TB via the first TRP (e.g., at or during the third timeinterval T3) and a second transmission of second layers of the first TBvia the second TRP (e.g., at or during the time interval T3′). The firstTB may be mapped to multiple layers comprising the first layers and thesecond layers, for example, if a multiple layer transmission for thefirst TB is supported. The first DCI may indicate a first HARQ-ACKfeedback for the first TB is to be sent/transmitted (e.g., at or duringa sixth time interval T6). The base station may send/transmit, from thesecond TRP to the wireless device, second DCI (e.g., at or during asecond time interval T2) indicating a transmission of a second TB via asecond PDSCH resource (e.g., at or during a fourth time interval T4).The second DCI may indicate a second HARQ-ACK feedback for the second TBis to be sent/transmitted (e.g., at or during a fifth time interval T5).The first TB may be associated with a first HARQ process (e.g., HARQprocess x). The second TB may be associated with a second HARQ process(e.g., HARQ process y). The second HARQ-ACK feedback may be determinedto be out-of-order, for example, based on the second HARQ-ACKinformation being feedbacked before the first HARQ-ACK information,while the second TB is sent/transmitted after transmissions of the firstTB.

FIG. 35B shows an example of out-of-order processing for multiple TRPsand/or multiple antenna panels. The wireless device may perform anexample method 3500. At step 3502, a wireless device may receive (e.g.,from the base station) one or more messages configuring resources (e.g.,multiple CORESETS, multiple TRPs, multiple antenna panels, etc.). Atstep 3504, the wireless device may determine whether the wireless devicecan use one or more resources (e.g., multiple CORESETS, multiple TRPs,multiple antenna panels, etc.), for example, for out-of-orderprocessing. At step 3506, the wireless device may determine to processat least the first TB sent/transmitted via the first TRP and process thesecond TB sent/transmitted via the second TRP, for example, forout-of-order processing and/or if the wireless device is capable ofusing resources (e.g., multiple CORESETS, multiple TRPs, multipleantenna panels, etc.). The wireless device may determine to process thefirst TB sent/transmitted via the first TRP, drop processing the firstTB sent/transmitted via the second TRP, and process the second TBsent/transmitted via the second TRP, for example, based on determiningthe second HARQ-ACK being out-of-order. The wireless device maydetermine to process the first TB sent/transmitted via the first TRP,drop processing the first TB sent/transmitted via the second TRP, andprocess the second TB sent/transmitted via the second TRP, for example,if the first TB sent/transmitted via the second TRP is a repetition(with the same or different RV value) of the first TB sent/transmittedvia the first TRP. The wireless device may be able to process alow-priority TB, for example, if the low-priority TB are repeated onmultiple TRPs, and/or if the wireless device determines (e.g., isconfigured/instructed/required) to process a high-priority TB with anout-of-order HARQ feedback. At step 3508, the wireless device maydetermine to process the first TB sent/transmitted via the first TRP anddrop other TB(s), for example, for out-of-order processing and/or if thewireless device is not capable of using resources (e.g., multipleCORESETS, multiple TRPs, multiple antenna panels, etc.). As describedherein, by using multiple TRPs and/or multiple antenna panels, a basestation and/or a wireless device may improve data transmission latencyand/or system throughput (e.g., if multiple TRPs and/or multiple antennapanels and out-of-order processing are supported).

The wireless device may determine to drop processing the first TBsent/transmitted via the first TRP, drop processing the first TBsent/transmitted via the second TRP, and process the second TBsent/transmitted via the second TRP, for example, based on the secondHARQ-ACK being out-of-order. The wireless device may determine to dropprocessing the first TB sent/transmitted via the first TRP, dropprocessing the first TB sent/transmitted via the second TRP, and processthe second TB sent/transmitted via the second TRP, for example, if oneor more second layers of the first TB sent/transmitted via the secondTRP are different from one or more first layers of the first TBsent/transmitted via the first TRP. The wireless device may be allowedto drop processing a low-priority TB, for example, if the low-priorityTB is sent/transmitted with different layers via multiple TRPs, and/orif the wireless device determines (e.g., isconfigured/instructed/required) to process a high-priority TB with anout-of-order HARQ feedback. As described herein, by determining anddropping the processing of the low-priority TB in multiple TRPs and/ormultiple antenna panels may reduce power consumption of the wirelessdevice.

The wireless device may determine whether to drop processing of alow-priority TB sent/transmitted via multiple TRPs, for example, basedon whether the transmission of the low-priority TB via the multiple TRPsare repetitions or multilayer transmissions, and/or if the wirelessdevice determines (e.g., is configured/instructed/required) to process ahigh-priority TB with an out-of-order HARQ feedback. As describedherein, by using multiple TRPs and/or multiple antenna panels, a basestation and/or a wireless device may improve data transmission latencyand/or system throughput (e.g., if multiple TRPs and/or multiple antennapanels and out-of-order processing are supported).

FIG. 36 shows an example of out-of-order processing for multiple TRPsand/or multiple antenna panels. Multiple TRPs and/or multiple antennapanels may be supported and out-of-order processing may be based onmultiple TRPs and/or antenna panels. A base station may send/transmit,from a first TRP (e.g., TRP 1) to a wireless device, first DCI (e.g., ator during a first time interval T1) indicating transmissions (orrepetitions) of a first TB via the first TRP and a second TRP (e.g., TRP2). The first DCI may indicate semi-persistent transmissions of thefirst TB via multiple TRPs. The transmissions of the first TB via thefirst TRP and via the second TRP may comprise a transmission of thefirst TB associated with a first RV value via the first TRP (e.g., at orduring a third time interval T3) and a repetition of the first TBassociated with a second RV value via the second TRP (e.g., at or duringa fifth time interval T5). The first RV value may be the same as ordifferent from the second RV value. The first DCI may indicate thetransmission of the first TB via a first PDSCH resource associated withthe first TRP and the transmission of the second TB via a third PDSCHresource associated with the second TRP. The transmissions of the firstTB via the first TRP and via the second TRP may comprise a firsttransmission of first layers of the first TB via the first TRP and asecond transmission of second layers of the first TB via the second TRP.The first TB may be mapped to multiple layers comprising the firstlayers and the second layers, for example, if a multiple layertransmission for the first TB is supported. The first DCI may indicatethat a first HARQ-ACK feedback is to be sent/transmitted (e.g., at orduring a seventh time interval T7). The base station may send/transmit,from the second TRP to the wireless device, second DCI (e.g., at orduring a second time interval T2) indicating a transmission of a secondTB via a second PDSCH resource (e.g., at or during a fourth timeinterval T4). The second DCI may indicate that a second HARQ-ACKfeedback is to be sent/transmitted (e.g., at or during a sixth timeinterval T6). The first TB may be associated with a first HARQ process(e.g., HARQ process x). The second TB may be associated with a secondHARQ process (e.g., HARQ process y). The second HARQ-ACK feedback may beout-of-order, for example, based on the second HARQ-ACK informationbeing feedbacked before the first HARQ-ACK information, while the secondTB is sent/transmitted after a first transmission of the first TB viathe first TRP and before a second transmission of the first TB via thesecond TRP.

The wireless device may determine to process the first TBsent/transmitted via the first TRP, process the second TBsent/transmitted via the second TRP, for example, based on the secondHARQ-ACK being out-of-order. The wireless device may drop processing thefirst TB sent/transmitted via the second TRP (e.g., at or during thefifth time interval T5), for example, based on determining to processthe second TB. The wireless device may determine to process the first TBsent/transmitted via the first TRP, process the second TBsent/transmitted via the second TRP, and drop processing the first TBsent/transmitted via the second TRP, for example, if the first TBsent/transmitted via the second TRP (e.g., at during the fifth timeinterval T5) is a repetition (with the same or different RV value) ofthe first TB sent/transmitted via the first TRP (e.g., at or during thethird time interval T3). The wireless device may process at least aportion of a low-priority TB transmission, for example, if thelow-priority TB are repeated on multiple TRPs, and/or if the wirelessdevice determines (e.g., is configured/instructed/required) to process ahigh-priority TB with an out-of-order HARQ feedback. As describedherein, by using multiple TRPs and/or multiple antenna panels, a basestation and/or a wireless device may improve data transmission latencyand/or system throughput (e.g., if multiple TRPs and/or multiple antennapanels and out-of-order processing are supported).

FIG. 37 shows an example of out-of-order processing for multiple TRPsand/or multiple antenna panels. The wireless device may perform anexample method 3700. At step 3702, a wireless device may receive one ormore RRC messages comprising configuration parameters of resources(e.g., CORESETs grouped into CORESET groups, multiple TRPs, multipleantenna panels, etc.). At step 3704, the wireless device may receivefirst DCI (e.g., via a first resource group). The wireless device mayreceive, via a first CORESET of the CORESETs, first DCI indicating afirst transmission of a first TB in a cell. At step 3706, the wirelessdevice may determine whether the wireless device uses different resourcegroups (e.g., different CORESET groups, different TRPs, differentantenna panels, etc.) For example, the wireless device may determine thefirst CORESET and the second CORESET are in (e.g., belonging to)different CORESET groups of the CORESET groups. At step 3708, thewireless device may receive second DCI (e.g., via a second resourcegroup). The wireless device may receive, via a second CORESET of theCORESETs, second DCI indicating a second transmission of a second TB inthe cell, for example, based on the first CORESET and the second CORESETbeing in (e.g., belonging to) different CORESET groups of the CORESETgroups. At step 3710, the wireless device may process a plurality ofchannels and/or data sent/transmitted via different resource groups. Thewireless device may process the second TB based on the second DCI andprocess the first TB based on the first DCI, for example, based on: atleast a portion of the second DCI being received after receiving atleast a portion of the first DCI, at least a portion of the secondtransmission occurring before at least a portion of the firsttransmission, and the first CORESET and the second CORESET being in(e.g., belonging to) different CORESET groups of the CORESET groups. Thewireless device may process the second TB based on the second DCI andprocess the first TB based on the first DCI, for example, based on: atleast a portion of the second DCI being received after receiving atleast a portion of the first DCI, at least a portion of the secondtransmission occurring after at least a portion of the firsttransmission, a second HARQ-ACK feedback for the second TB beingscheduled to be sent/transmitted before a first HARQ-ACK feedback forthe first TB, and the first CORESET and the second CORESET being in(e.g., belonging to) different CORESET groups of the CORESET groups. Thewireless device may send/transmit first HARQ-ACK information for thefirst TB based on the processing of the first TB, and send/transmitsecond HARQ-ACK information for the second TB based on processing of thesecond TB.

At step 3712, the wireless device may receive third DCI (e.g., via asame resource group associated with the first DCI). The wireless devicemay receive, via a third CORESET of the CORESETs, third DCI indicating athird transmission of a TB (e.g., a third TB) in the cell, for example,based on the first CORESET and the third CORESET being in (e.g.,belonging to) the same CORESET group of the CORESET groups. At step3714, the wireless device may process and drop channels and/or datasent/transmitted via the same resource group. The wireless device mayprocess the second TB based on the second DCI and drop the processing ofthe first TB, for example, based on: at least a portion of the secondDCI being received after receiving at least a portion of the first DCI,at least a portion of the second transmission occurring after at least aportion of the first transmission, a second HARQ-ACK feedback for thesecond TB being scheduled to be sent/transmitted before a first HARQ-ACKfeedback for the first TB, and the first CORESET and the second CORESETbeing in (e.g., belonging to) the same CORESET group of the CORESETgroups. The wireless device may send/transmit first HARQ-ACK informationfor the first TB based on the dropping. Processing a TB may comprise atleast one of: performing a channel estimation based on a DM-RS of aPDSCH, demodulating and decoding the TB based on the channel estimation,and/or generating HARQ-ACK information for the TB. Dropping and/or notprocessing a TB may comprise at least one of: ignoring the TB; stoppingprocessing the TB; avoiding processing the TB; not storing the TB; notconfiguring to receive the TB; not receiving the TB; not scheduling toreceive the TB; skipping allocating the TB to a resource/process;skipping decoding the TB; skipping generating an ACK or NACK for the TB;refraining from performing a channel estimation based on a DM-RS of aPDSCH; refraining from demodulating and decoding the TB; and/orrefraining from generating HARQ-ACK information for the TB, etc. Asdescribed herein, by using improved out-of-order processing and multipleresources (e.g., multiple CORESETS, multiple TRPs and/or multipleantenna panels), a base station and/or a wireless device may improvedata transmission latency and/or system throughput (e.g., if multipleTRPs and/or multiple antenna panels and out-of-order processing aresupported).

One or more transmissions of control information (e.g., DCI, UCI, aHARQ-ACK) and/or data (e.g., a TB) may be transmitted between wirelessdevices via a sidelink channel (e.g., a physical sidelink controlchannel, a physical sidelink shared channel, etc.). Multiple TRPs may bereplaced with multiple base stations and/or multiple cells. PrioritizingTBs, and/or TB processing and/or a TB dropping decision may be, forexample, based on device types, frequency, and/or other variables withrespect to the DCI or a device sending the DCI described herein.Prioritizing HARQ-ACK information and/or HARQ-ACK information processingand/or a HARQ-ACK dropping decision may be, for example, based on devicetypes, frequency, overlapping transmissions (e.g., TBs, HARQ-ACKs, etc.)and/or other variables with respect to the DCI or a device sending theDCI described herein.

A wireless device may perform a method comprising multiple operations.The wireless device may receive configuration parameters of a pluralityof control resource sets (CORESETs) grouped into a plurality of controlresource set (CORESET) groups. The plurality of CORESETs may comprise afirst CORESET and a second CORESET. The wireless device may receive, viaa channel associated with the first CORESET of the plurality ofCORESETs, first downlink control information (DCI) indicating a firstscheduled transmission of a first transport block (TB). The wirelessdevice may receive, via a channel associated with the second CORESET ofthe plurality of CORESETs, second DCI indicating a second scheduledtransmission of a second TB. The wireless device may receive the secondDCI after receiving the first DCI and based on the first CORESET and thesecond CORESET being in different CORESET groups. The second scheduledtransmission may start earlier than the first scheduled transmission.The wireless device may receive the second TB and the first TB. Thewireless device may transmit a first acknowledgment for the first TB anda second acknowledgement for the second TB. The wireless device mayprocess the second TB and the first TB, for example, based on the firstCORESET and the second CORESET being in different CORESET groups. Thewireless device may receive the second TB and the first TB, for example,based on the first CORESET and the second CORESET being in differentCORESET groups. The receiving the second TB may start earlier than astart of the receiving the first TB. The receiving the second TB maystart earlier than completion of the receiving the first TB. Thereceiving the second TB may be completed prior to a start of thereceiving the first TB. Completion of the receiving the second DCI maybe later than completion of the receiving the first DCI. A first CORESETgroup associated with a first CORESET group index may comprise the firstCORESET, and a second CORESET group associated with a second CORESETgroup index may comprise the second CORESET. The transmitting the firstacknowledgment for the first TB and the second acknowledgement for thesecond TB by the wireless device may comprise: based on the firstCORESET and the second CORESET being in different CORESET groups,transmitting the second acknowledgement prior to transmitting the firstacknowledgment. The transmitting the first acknowledgment for the firstTB and the second acknowledgement for the second TB by the wirelessdevice may comprise: based on the first CORESET and the second CORESETbeing in different CORESET groups, transmitting the secondacknowledgement after transmitting the first acknowledgment. Thewireless device may, based on the first CORESET and the second CORESETbeing in different CORESET groups, process a plurality of transportblocks (TBs) comprising the second TB and the first TB. The processingthe plurality of TBs may comprise at least one of: receiving theplurality of TBs; allocating the plurality of TBs to different hybridautomatic repeat request (HARQ) processes; or decoding the plurality ofTBs. The wireless device may, based on the first CORESET and a thirdCORESET being in a same CORESET group, receive the first TB; and drop athird TB indicated by third DCI associated with the third CORESET. Thedropping the third TB may comprise at least one of: skipping allocatingthe third TB to a second hybrid automatic repeat request (HARQ) process;skipping decoding the third TB; or skipping generating a thirdacknowledgement for the third TB. The first acknowledgement may beassociated with a first hybrid automatic repeat request (HARQ) processof the first TB, and the second acknowledgement may be associated with asecond HARQ process of the second TB different from the first HARQprocess. The configuration parameters of the plurality of the CORESETsmay comprise at least one of: a first CORESET group index indicating afirst CORESET group comprising the first CORESET; or a second CORESETgroup index indicating a second CORESET group comprising the secondCORESET. The configuration parameters of the plurality of the CORESETsmay comprise at least one of: a frequency resource indication; or a timedomain duration indication. The configuration parameters of theplurality of the CORESETs may comprise an indication of control channelelement (CCE) to resource element group (REG) mapping type. The wirelessdevice may allocate the first TB to a first hybrid automatic repeatrequest (HARQ) process; decode the first TB; and/or generate the firstacknowledgement for the first TB. The first acknowledgement may be apositive acknowledgement generated based on the decoding the first TBbeing successful. The first acknowledgement may be a negativeacknowledgement generated based on the decoding the first TB beingunsuccessful. The wireless device may allocate the second TB to a secondHARQ process; decode the second TB; and/or generate the secondacknowledgement for the second TB. The second acknowledgement may be apositive acknowledgement generated based on the decoding the second TBbeing successful. The second acknowledgement may be a negativeacknowledgement generated based on the decoding the second TB beingunsuccessful. The wireless device may monitor a downlink control channelvia the first CORESET for receiving the first DCI. The wireless devicemay monitor a downlink control channel via the second CORESET forreceiving the second DCI. A wireless device may comprise one or moreprocessors; and memory storing instructions that, when executed by theone or more processors, cause the wireless device to perform thedescribed method, additional operations and/or include the additionalelements. A system may comprise a wireless device configured to performthe described method, additional operations and/or include theadditional elements; and a base station configured to send/transmit theconfiguration parameters. A computer-readable medium may storeinstructions that, when executed, cause performance of the describedmethod, additional operations and/or include the additional elements.

A wireless device may perform a method comprising multiple operations.The wireless device may receive configuration parameters of a pluralityof control resource sets (CORESETs) grouped into a plurality of controlresource set (CORESET) groups, wherein the plurality of CORESETscomprise a first CORESET and a second CORESET. The wireless device mayreceive, via a channel associated with the first CORESET, first downlinkcontrol information (DCI) indicating a first scheduled transmission of afirst transport block (TB). The wireless device may receive, via achannel associated with the second CORESET, second DCI indicating asecond scheduled transmission of a second TB. The wireless device mayreceive the second DCI after receiving the first DCI. The secondscheduled transmission may start earlier than the first scheduledtransmission. The wireless device may, based on the first CORESET andthe second CORESET being in different CORESET groups, process the secondTB and the first TB. The wireless device may transmit a first uplinksignal associated with the first TB and a second uplink signalassociated with the second TB. The receiving the second DCI by thewireless device may be based on the first CORESET and the second CORESETbeing in different CORESET groups. The processing the second TB maycomprise at least one of: receiving the second TB; allocating the secondTB to a second hybrid automatic repeat request (HARQ) process differentfrom a first HARQ process for the first TB; decoding the second TB; orgenerating the second uplink signal to transmit the second TB. Theprocessing the first TB may comprise at least one of: receiving thefirst TB; allocating the first TB to a first hybrid automatic repeatrequest (HARQ) process different from a second HARQ process for thesecond TB; decoding the first TB; or generating the first uplink signalto transmit the first TB. The first uplink signal may comprise at leastone of: a first acknowledgment for the first TB; or a first uplinkshared channel signal comprising the first TB. The wireless device may,based on the first CORESET and the second CORESET being in differentCORESET groups, receive the second TB based on the second DCI andreceive the first TB based on the first DCI. The wireless device may,based on the first CORESET and a third CORESET being in a same CORESETgroup, receive the first TB and drop a third TB indicated by third DCIassociated with the third CORESET. The dropping the third TB maycomprise at least one of: skipping allocating the third TB to a secondhybrid automatic repeat request (HARQ) process; skipping decoding thethird TB; or skipping generating a third acknowledgement for the thirdTB. A wireless device may comprise one or more processors; and memorystoring instructions that, when executed by the one or more processors,cause the wireless device to perform the described method, additionaloperations and/or include the additional elements. A system may comprisea wireless device configured to perform the described method, additionaloperations and/or include the additional elements; and a base stationconfigured to send/transmit the configuration parameters. Acomputer-readable medium may store instructions that, when executed,cause performance of the described method, additional operations and/orinclude the additional elements.

A wireless device may perform a method comprising multiple operations.The wireless device may receive configuration parameters of a pluralityof control resource sets (CORESETs) grouped into a plurality of controlresource set (CORESET) groups, wherein the plurality of CORESETscomprise a first CORESET and a second CORESET. The wireless device mayreceive, via a channel associated with the first CORESET, first downlinkcontrol information (DCI) indicating a first scheduled transmission of afirst transport block (TB). The wireless device may receive, via achannel associated with the second CORESET, second DCI indicating asecond scheduled transmission of a second TB. The second scheduledtransmission may start earlier than the first scheduled transmission.The wireless device may, based on the first CORESET and the secondCORESET being in different CORESET groups, process the second TB andprocess the first TB after processing the second TB. The processing thefirst TB may comprise generating a first uplink signal to transmit thefirst TB, and the processing the second TB may comprise generating asecond uplink signal to transmit the second TB. The wireless device may,based on the first CORESET and the second CORESET being in differentCORESET groups, transmit the second TB based on the second DCI, andtransmit the first TB based on the first DCI. A wireless device maycomprise one or more processors; and memory storing instructions that,when executed by the one or more processors, cause the wireless deviceto perform the described method, additional operations and/or includethe additional elements. A system may comprise a wireless deviceconfigured to perform the described method, additional operations and/orinclude the additional elements; and a base station configured tosend/transmit the configuration parameters. A computer-readable mediummay store instructions that, when executed, cause performance of thedescribed method, additional operations and/or include the additionalelements.

A wireless device may perform a method comprising multiple operations.The wireless device may receive first downlink control information (DCI)indicating information associated with a first signal, wherein the firstDCI comprises a priority indicator field indicating a first priorityvalue. The wireless device may receive second DCI indicating informationassociated with a second signal. The wireless device may, based on thesecond DCI not comprising a priority indicator field, determine a secondpriority value. The wireless device may, based on the first priorityvalue and the determined second priority value, transmit the firstsignal and drop transmitting the second signal. The first DCI mayfurther indicate a first downlink signal associated with a firsttransport block, and the second DCI may further indicate a seconddownlink signal associated with a second transport block. The firstsignal may be an uplink control channel signal associated with a firstdownlink shared channel signal indicated by the first DCI, and thesecond signal may be an uplink control channel signal associated with asecond downlink shared channel signal indicated by the second DCI. Thewireless device may receive, based on the first DCI, a first transportblock and/or determine a first acknowledgement for the first transportblock. The transmitting the first signal may comprise transmitting,based on the information associated with the first signal, the firstacknowledgment for the first transport block. The information associatedwith the first signal may comprise at least one of: an uplink resourceassociated with the first signal; or a timing value associated with thefirst signal. The information associated with the second signal maycomprise at least one of: an uplink resource associated with the secondsignal; or a timing value associated with the second signal. Thedropping transmitting the second signal may be based on a timing valueassociated with the second signal. A scheduled transmission of the firstsignal may overlap in time with a scheduled transmission of the secondsignal. The dropping transmitting the second signal may comprise atleast one of: refraining from demodulating of a downlink signalindicated by the second DCI; refraining from decoding of the downlinksignal indicated by the second DCI; refraining from generatingacknowledgment information associated with the second signal; orclearing buffered data for a hybrid automatic repeat request (HARQ)process associated with the second signal. The dropping transmitting thesecond signal may be based on the first priority value being greaterthan the determined second priority value. A wireless device maycomprise one or more processors; and memory storing instructions that,when executed by the one or more processors, cause the wireless deviceto perform the described method, additional operations and/or includethe additional elements. A system may comprise a wireless deviceconfigured to perform the described method, additional operations and/orinclude the additional elements; and a base station configured tosend/transmit the first DCI. A computer-readable medium may storeinstructions that, when executed, cause performance of the describedmethod, additional operations and/or include the additional elements.

A wireless device may perform a method comprising multiple operations.The wireless device may receive first downlink control information (DCI)indicating a first transmission associated with a first signal, whereinthe first DCI comprises a priority indicator field indicating a firstpriority value. The wireless device may receive second DCI indicating asecond transmission associated with a second signal. The wireless devicemay, based on the second DCI not comprising a priority indicator field,determine a second priority value. The wireless device may, based on thefirst priority value being greater than the determined second priorityvalue, transmit the first signal without transmitting the second signal.The wireless device may drop transmitting the second signal based on atleast one of: the first priority value being greater than the determinedsecond priority value; or a timing value associated with the secondsignal. The first priority value may be associated with the firstsignal, and the determined second priority value may be associated withthe second signal. The first transmission may be a first downlink signaltransmission associated with a first transport block, and the secondtransmission may be a second downlink signal transmission associatedwith a second transport block. The wireless device may receive, based onthe first DCI, a first transport block and determine a firstacknowledgement for the first transport block. The transmitting thefirst signal may comprise transmitting, based on information associatedwith the first signal, the first acknowledgment for the first transportblock. A wireless device may comprise one or more processors; and memorystoring instructions that, when executed by the one or more processors,cause the wireless device to perform the described method, additionaloperations and/or include the additional elements. A system may comprisea wireless device configured to perform the described method, additionaloperations and/or include the additional elements; and a base stationconfigured to send/transmit the first DCI. A computer-readable mediummay store instructions that, when executed, cause performance of thedescribed method, additional operations and/or include the additionalelements.

A wireless device may perform a method comprising multiple operations.The wireless device may receive first downlink control information (DCI)indicating information associated with a first signal, wherein the firstDCI comprises a priority indicator field indicating a first priorityvalue. The wireless device may receive second DCI indicating informationassociated with a second signal. The wireless device may process thefirst signal and dropping processing the second signal. The processingthe first signal and the dropping processing the second signal may bebased on: the priority indicator field indicating a first priorityvalue; and the second DCI not comprising a priority indicator field. Thewireless device may, based on the second DCI not comprising a priorityindicator field, determine a second priority value. The droppingprocessing the second signal may be based on the first priority valuebeing greater than the determined second priority value. The wirelessdevice may, based on the second DCI not comprising a priority indicatorfield, set a second priority value associated with the second signal asa first value. The first DCI may further indicate a first downlinksignal associated with a first transport block, and the second DCI mayfurther indicate a second downlink signal associated with a secondtransport block. The dropping processing the second signal may compriseat least one of: refraining from receiving a transport block indicatedby the second DCI; refraining from demodulating of the transport blockindicated by the second DCI; refraining from decoding of the transportblock indicated by the second DCI; refraining from generatingacknowledgment information for the transport block indicated by thesecond DCI; clearing buffered data for a hybrid automatic repeat request(HARQ) process associated with the second signal; or refraining fromtransmitting an acknowledgement for the transport block indicated by thesecond DCI. The processing the first signal may comprise at least oneof: receiving a transport block indicated by the first DCI; demodulatingthe transport block indicated by the first DCI; decoding the transportblock indicated by the first DCI; generating acknowledgment informationfor the transport block indicated by the first DCI; buffering data for ahybrid automatic repeat request (HARQ) process associated with the firstsignal; or transmitting an acknowledgement for the transport blockindicated by the first DCI. A wireless device may comprise one or moreprocessors; and memory storing instructions that, when executed by theone or more processors, cause the wireless device to perform thedescribed method, additional operations and/or include the additionalelements. A system may comprise a wireless device configured to performthe described method, additional operations and/or include theadditional elements; and a base station configured to send/transmit thefirst DCI. A computer-readable medium may store instructions that, whenexecuted, cause performance of the described method, additionaloperations and/or include the additional elements.

One or more of the operations described herein may be conditional. Forexample, one or more operations may be performed if certain criteria aremet, such as in a wireless device, a base station, a radio environment,a network, a combination of the above, and/or the like. Example criteriamay be based on one or more conditions such as wireless device and/ornetwork node configurations, traffic load, initial system set up, packetsizes, traffic characteristics, a combination of the above, and/or thelike. If the one or more criteria are met, various examples may be used.It may be possible to implement any portion of the examples describedherein in any order and based on any condition.

A base station may communicate with one or more of wireless devices.Wireless devices and/or base stations may support multiple technologies,and/or multiple releases of the same technology. Wireless devices mayhave some specific capability(ies) depending on wireless device categoryand/or capability(ies). A base station may comprise multiple sectors,cells, and/or portions of transmission entities. A base stationcommunicating with a plurality of wireless devices may refer to a basestation communicating with a subset of the total wireless devices in acoverage area. Wireless devices referred to herein may correspond to aplurality of wireless devices compatible with a given LTE, 5G, or other3GPP or non-3GPP release with a given capability and in a given sectorof a base station. A plurality of wireless devices may refer to aselected plurality of wireless devices, a subset of total wirelessdevices in a coverage area, and/or any group of wireless devices. Suchdevices may operate, function, and/or perform based on or according todrawings and/or descriptions herein, and/or the like. There may be aplurality of base stations and/or a plurality of wireless devices in acoverage area that may not comply with the disclosed methods, forexample, because those wireless devices and/or base stations may performbased on older releases of LTE, 5G, or other 3GPP or non-3GPPtechnology.

One or more parameters, fields, and/or Information elements (IEs), maycomprise one or more information objects, values, and/or any otherinformation. An information object may comprise one or more otherobjects. At least some (or all) parameters, fields, IEs, and/or the likemay be used and can be interchangeable depending on the context. If ameaning or definition is given, such meaning or definition controls.

One or more elements in examples described herein may be implemented asmodules. A module may be an element that performs a defined functionand/or that has a defined interface to other elements. The modules maybe implemented in hardware, software in combination with hardware,firmware, wetware (e.g., hardware with a biological element) or acombination thereof, all of which may be behaviorally equivalent. Forexample, modules may be implemented as a software routine written in acomputer language configured to be executed by a hardware machine (suchas C, C++, Fortran, Java, Basic, Matlab or the like) or amodeling/simulation program such as Simulink, Stateflow, GNU Octave, orLab VIEWMathScript. Additionally or alternatively, it may be possible toimplement modules using physical hardware that incorporates discrete orprogrammable analog, digital and/or quantum hardware. Examples ofprogrammable hardware may comprise: computers, microcontrollers,microprocessors, application-specific integrated circuits (ASICs); fieldprogrammable gate arrays (FPGAs); and/or complex programmable logicdevices (CPLDs). Computers, microcontrollers and/or microprocessors maybe programmed using languages such as assembly, C, C++ or the like.FPGAs, ASICs and CPLDs are often programmed using hardware descriptionlanguages (HDL), such as VHSIC hardware description language (VHDL) orVerilog, which may configure connections between internal hardwaremodules with lesser functionality on a programmable device. Theabove-mentioned technologies may be used in combination to achieve theresult of a functional module.

One or more features described herein may be implemented in acomputer-usable data and/or computer-executable instructions, such as inone or more program modules, executed by one or more computers or otherdevices. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other data processing device. The computer executableinstructions may be stored on one or more computer readable media suchas a hard disk, optical disk, removable storage media, solid statememory, RAM, etc. The functionality of the program modules may becombined or distributed as desired. The functionality may be implementedin whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike. Particular data structures may be used to more effectivelyimplement one or more features described herein, and such datastructures are contemplated within the scope of computer executableinstructions and computer-usable data described herein.

A non-transitory tangible computer readable media may compriseinstructions executable by one or more processors configured to causeoperations of multi-carrier communications described herein. An articleof manufacture may comprise a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g., a wirelessdevice, wireless communicator, a wireless device, a base station, andthe like) to allow operation of multi-carrier communications describedherein. The device, or one or more devices such as in a system, mayinclude one or more processors, memory, interfaces, and/or the like.Other examples may comprise communication networks comprising devicessuch as base stations, wireless devices or user equipment (wirelessdevice), servers, switches, antennas, and/or the like. A network maycomprise any wireless technology, including but not limited to,cellular, wireless, WiFi, 4G, 5G, any generation of 3GPP or othercellular standard or recommendation, any non-3GPP network, wirelesslocal area networks, wireless personal area networks, wireless ad hocnetworks, wireless metropolitan area networks, wireless wide areanetworks, global area networks, satellite networks, space networks, andany other network using wireless communications. Any device (e.g., awireless device, a base station, or any other device) or combination ofdevices may be used to perform any combination of one or more of stepsdescribed herein, including, for example, any complementary step orsteps of one or more of the above steps.

Although examples are described above, features and/or steps of thoseexamples may be combined, divided, omitted, rearranged, revised, and/oraugmented in any desired manner Various alterations, modifications, andimprovements will readily occur to those skilled in the art. Suchalterations, modifications, and improvements are intended to be part ofthis description, though not expressly stated herein, and are intendedto be within the spirit and scope of the descriptions herein.Accordingly, the foregoing description is by way of example only, and isnot limiting.

What is claimed is:
 1. A method comprising: receiving, by a wirelessdevice, configuration parameters of a plurality of control resource sets(CORESETs) grouped into a plurality of control resource set (CORESET)groups; receiving, via a channel associated with a first CORESET of theplurality of CORESETs, first downlink control information (DCI)indicating a first scheduled transmission of a first transport block(TB); after receiving the first DCI and based on the first CORESET and asecond CORESET of the plurality of CORESETs being in different CORESETgroups, receiving, via a channel associated with the second CORESET,second DCI indicating a second scheduled transmission of a second TB,wherein the second scheduled transmission starts earlier than the firstscheduled transmission; receiving the second TB; receiving the first TB;and transmitting a first acknowledgment for the first TB and a secondacknowledgement for the second TB.
 2. The method of claim 1, furthercomprising: processing the second TB and the first TB such that thereceiving the second TB and the receiving the first TB are based on thefirst CORESET and the second CORESET being in different CORESET groups.3. The method of claim 1, wherein the receiving the second TB startsearlier than a start of the receiving the first TB.
 4. The method ofclaim 1, wherein the receiving the second TB starts earlier thancompletion of the receiving the first TB.
 5. The method of claim 1,wherein the receiving the second TB is completed prior to a start of thereceiving the first TB.
 6. The method of claim 1, wherein completion ofthe receiving the second DCI is later than completion of the receivingthe first DCI.
 7. The method of claim 1, wherein a first CORESET groupassociated with a first CORESET group index comprises the first CORESET,and wherein a second CORESET group associated with a second CORESETgroup index comprises the second CORESET.
 8. The method of claim 1,wherein the transmitting the first acknowledgment for the first TB andthe second acknowledgement for the second TB comprises: based on thefirst CORESET and the second CORESET being in different CORESET groups,transmitting the second acknowledgement prior to transmitting the firstacknowledgment.
 9. The method of claim 1, wherein the transmitting thefirst acknowledgment for the first TB and the second acknowledgement forthe second TB comprises: based on the first CORESET and the secondCORESET being in different CORESET groups, transmitting the secondacknowledgement after transmitting the first acknowledgment.
 10. Amethod comprising: receiving, by a wireless device, configurationparameters of a plurality of control resource sets (CORESETs) groupedinto a plurality of control resource set (CORESET) groups; receiving,via a channel associated with a first CORESET of the plurality ofCORESETs, first downlink control information (DCI) indicating a firstscheduled transmission of a first transport block (TB); after receivingthe first DCI, receiving, via a channel associated with a second CORESETof the plurality of CORESETs, second DCI indicating a second scheduledtransmission of a second TB, wherein the second scheduled transmissionstarts earlier than the first scheduled transmission; based on the firstCORESET and the second CORESET being in different CORESET groups,processing the second TB and the first TB; and transmitting a firstuplink signal associated with the first TB and a second uplink signalassociated with the second TB.
 11. The method of claim 10, wherein thereceiving the second DCI is based on the first CORESET and the secondCORESET being in different CORESET groups.
 12. The method of claim 10,wherein the processing the second TB comprises at least one of:receiving the second TB; allocating the second TB to a second hybridautomatic repeat request (HARQ) process different from a first HARQprocess for the first TB; decoding the second TB; or generating thesecond uplink signal to transmit the second TB.
 13. The method of claim10, wherein the processing the first TB comprises at least one of:receiving the first TB; allocating the first TB to a first hybridautomatic repeat request (HARQ) process different from a second HARQprocess for the second TB; decoding the first TB; or generating thefirst uplink signal to transmit the first TB.
 14. The method of claim10, wherein the first uplink signal comprises at least one of: a firstacknowledgment for the first TB; or a first uplink shared channel signalcomprising the first TB.
 15. The method of claim 10, further comprising:based on the first CORESET and the second CORESET being in differentCORESET groups: receiving the second TB based on the second DCI; andreceiving the first TB based on the first DCI.
 16. The method of claim10, further comprising: based on the first CORESET and a third CORESETbeing in a same CORESET group: receiving the first TB; and dropping athird TB indicated by third DCI associated with the third CORESET. 17.The method of claim 10, wherein the dropping the third TB comprises atleast one of: skipping allocating the third TB to a second hybridautomatic repeat request (HARQ) process; skipping decoding the third TB;or skipping generating a third acknowledgement for the third TB.
 18. Amethod comprising: receiving, by a wireless device, configurationparameters of a plurality of control resource sets (CORESETs) groupedinto a plurality of control resource set (CORESET) groups; receiving,via a channel associated with a first CORESET of the plurality ofCORESETs, first downlink control information (DCI) indicating a firstscheduled transmission of a first transport block (TB); receiving, via achannel associated with a second CORESET of the plurality of CORESETs,second DCI indicating a second scheduled transmission of a second TB,wherein the second scheduled transmission starts earlier than the firstscheduled transmission; and based on the first CORESET and the secondCORESET being in different CORESET groups: processing the second TB; andprocessing the first TB after processing the second TB.
 19. The methodof claim 18, wherein the processing the first TB comprises generating afirst uplink signal to transmit the first TB, and wherein the processingthe second TB comprises generating a second uplink signal to transmitthe second TB.
 20. The method of claim 18, further comprising: based onthe first CORESET and the second CORESET being in different CORESETgroups: transmitting the second TB based on the second DCI; andtransmitting the first TB based on the first DCI.